https://pulp.plan.io/https://pulp.plan.io/favicon.ico2019-06-21T14:32:09ZPulpPulp - Story #5008: As a user, I can enforce content specific uniqueness constaints in a repo versionhttps://pulp.plan.io/issues/5008?journal_id=449572019-06-21T14:32:09Zttereshcttereshc@redhat.com
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/44957/diff?detail_id=45385">diff</a>)</li></ul> Pulp - Story #5008: As a user, I can enforce content specific uniqueness constaints in a repo versionhttps://pulp.plan.io/issues/5008?journal_id=449582019-06-21T14:34:13Zttereshcttereshc@redhat.com
<ul><li><strong>Related to</strong> <i><a class="issue tracker-2 status-11 priority-6 priority-default closed" href="/issues/4028">Task #4028</a>: Prevent duplicate files in repositories</i> added</li></ul> Pulp - Story #5008: As a user, I can enforce content specific uniqueness constaints in a repo versionhttps://pulp.plan.io/issues/5008?journal_id=449602019-06-21T14:34:21Zttereshcttereshc@redhat.com
<ul><li><strong>Related to</strong> <i><a class="issue tracker-3 status-11 priority-6 priority-default closed" href="/issues/4898">Story #4898</a>: As a user, no "duplicated" content is present in a repo version</i> added</li></ul> Pulp - Story #5008: As a user, I can enforce content specific uniqueness constaints in a repo versionhttps://pulp.plan.io/issues/5008?journal_id=450992019-06-25T14:48:02Zamacdona@redhat.comaustin@redhat.com
<ul><li><strong>Triaged</strong> changed from <i>No</i> to <i>Yes</i></li></ul> Pulp - Story #5008: As a user, I can enforce content specific uniqueness constaints in a repo versionhttps://pulp.plan.io/issues/5008?journal_id=461172019-07-30T13:36:57Zttereshcttereshc@redhat.com
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/46117/diff?detail_id=46613">diff</a>)</li></ul> Pulp - Story #5008: As a user, I can enforce content specific uniqueness constaints in a repo versionhttps://pulp.plan.io/issues/5008?journal_id=461182019-07-30T13:38:06Zttereshcttereshc@redhat.com
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/46118/diff?detail_id=46614">diff</a>)</li></ul> Pulp - Story #5008: As a user, I can enforce content specific uniqueness constaints in a repo versionhttps://pulp.plan.io/issues/5008?journal_id=461252019-07-30T14:50:02Zamacdona@redhat.comaustin@redhat.com
<ul><li><strong>Sprint</strong> set to <i>Sprint 56</i></li></ul> Pulp - Story #5008: As a user, I can enforce content specific uniqueness constaints in a repo versionhttps://pulp.plan.io/issues/5008?journal_id=461282019-07-30T16:31:11Zbmbouterbmbouter@redhat.com
<ul></ul><p>This all looks good. Should we convert this to a story? To me in the changelog this would make the most sense as a new feature in the pulpcore-plugin package. What do you think?</p> Pulp - Story #5008: As a user, I can enforce content specific uniqueness constaints in a repo versionhttps://pulp.plan.io/issues/5008?journal_id=461472019-07-31T13:40:56Zttereshcttereshc@redhat.com
<ul><li><strong>Tracker</strong> changed from <i>Issue</i> to <i>Story</i></li><li><strong>Subject</strong> changed from <i>No way to enforce content specific uniqueness constaints in a repo version</i> to <i>As a user, I can enforce content specific uniqueness constaints in a repo version</i></li><li><strong>% Done</strong> set to <i>0</i></li></ul> Pulp - Story #5008: As a user, I can enforce content specific uniqueness constaints in a repo versionhttps://pulp.plan.io/issues/5008?journal_id=461482019-07-31T14:07:57Zbmbouterbmbouter@redhat.com
<ul><li><strong>Groomed</strong> changed from <i>No</i> to <i>Yes</i></li><li><strong>Sprint Candidate</strong> changed from <i>No</i> to <i>Yes</i></li></ul><p>This looks good to me. Thank you for recapping <a class="user active" href="https://pulp.plan.io/users/281">ttereshc</a>!</p> Pulp - Story #5008: As a user, I can enforce content specific uniqueness constaints in a repo versionhttps://pulp.plan.io/issues/5008?journal_id=462272019-08-02T13:14:55Zrchan
<ul><li><strong>Sprint</strong> changed from <i>Sprint 56</i> to <i>Sprint 57</i></li></ul> Pulp - Story #5008: As a user, I can enforce content specific uniqueness constaints in a repo versionhttps://pulp.plan.io/issues/5008?journal_id=470182019-08-26T14:31:01Zrchan
<ul><li><strong>Sprint</strong> changed from <i>Sprint 57</i> to <i>Sprint 58</i></li></ul> Pulp - Story #5008: As a user, I can enforce content specific uniqueness constaints in a repo versionhttps://pulp.plan.io/issues/5008?journal_id=473642019-09-10T18:53:20Zbmbouterbmbouter@redhat.com
<ul><li><strong>Status</strong> changed from <i>NEW</i> to <i>ASSIGNED</i></li><li><strong>Assignee</strong> set to <i>bmbouter</i></li></ul> Pulp - Story #5008: As a user, I can enforce content specific uniqueness constaints in a repo versionhttps://pulp.plan.io/issues/5008?journal_id=474682019-09-13T14:59:25Zrchan
<ul><li><strong>Sprint</strong> changed from <i>Sprint 58</i> to <i>Sprint 59</i></li></ul> Pulp - Story #5008: As a user, I can enforce content specific uniqueness constaints in a repo versionhttps://pulp.plan.io/issues/5008?journal_id=479412019-09-27T10:55:00Zdaviddavis
<ul><li><strong>Sprint/Milestone</strong> set to <i>3.0.0</i></li></ul> Pulp - Story #5008: As a user, I can enforce content specific uniqueness constaints in a repo versionhttps://pulp.plan.io/issues/5008?journal_id=479582019-09-27T13:46:26Zrchan
<ul><li><strong>Sprint</strong> changed from <i>Sprint 59</i> to <i>Sprint 60</i></li></ul> Pulp - Story #5008: As a user, I can enforce content specific uniqueness constaints in a repo versionhttps://pulp.plan.io/issues/5008?journal_id=482682019-10-07T22:06:31Zbmbouterbmbouter@redhat.com
<ul><li><strong>Status</strong> changed from <i>ASSIGNED</i> to <i>POST</i></li></ul><p>PR available at: <a href="https://github.com/pulp/pulpcore/pull/331" class="external">https://github.com/pulp/pulpcore/pull/331</a></p> Pulp - Story #5008: As a user, I can enforce content specific uniqueness constaints in a repo versionhttps://pulp.plan.io/issues/5008?journal_id=483172019-10-08T19:52:00Zbmbouterbmbouter@redhat.com
<ul><li><strong>Status</strong> changed from <i>POST</i> to <i>MODIFIED</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>100</i></li></ul><p>Applied in changeset <a class="changeset" title="Add repo_key support for `add_content` The `Content` model now supports a `repo_key` attribute w..." href="https://pulp.plan.io/projects/pulp/repository/pulpcore/revisions/b41a0923183c4316401349fb4f823b76433e9ed9">pulpcore|b41a0923183c4316401349fb4f823b76433e9ed9</a>.</p> Pulp - Story #5008: As a user, I can enforce content specific uniqueness constaints in a repo versionhttps://pulp.plan.io/issues/5008?journal_id=509742019-12-13T17:28:50Zbmbouterbmbouter@redhat.com
<ul><li><strong>Status</strong> changed from <i>MODIFIED</i> to <i>CLOSED - CURRENTRELEASE</i></li></ul>