<div dir="ltr"><div>Thanks for all the feedback! With many +1s and no -1s, I'm going to make this change tomorrow. I'll send out links to the result when it is done.<br><br></div>-Brian<br><br><div><div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Mar 5, 2018 at 12:43 PM, Jeff Ortel <span dir="ltr"><<a href="mailto:jortel@redhat.com" target="_blank">jortel@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<font face="DejaVu Sans">+1</font><div><div class="h5"><br>
<br>
<div class="m_-6615441638576296832moz-cite-prefix">On 03/02/2018 04:17 PM, Brian Bouterse
wrote:<br>
</div>
</div></div><blockquote type="cite"><div><div class="h5">
<div dir="ltr">
<div>
<div>
<div>
<div>
<div>Redmine's milestone feature allows for roadmap
pages to be published for each project on <a href="http://pulp.plan.io" target="_blank">pulp.plan.io</a>
like this one [0]. Currently all projects use a single
set of milestones from the main 'Pulp' project on
Redmine which is what defines the Sprints, e.g.
'Sprint 22'. This creates a few problems:<br>
<br>
</div>
1. Redmine projects can't use the milestone feature of
Redmine for release planning. This is unfortunate since
the milestone feature is a good release planning and
roadmapping tool.<br>
<br>
</div>
2. Any project that does use milestones can't have issues
associated with milestones also on a sprint. Like pulp_rpm
pulp3 issues [0].<br>
<br>
</div>
I'm interested in hearing any solution on resolving these
issues, but I also have one to share:<br>
<br>
</div>
1. We could create a custom field called 'Sprint' and make
that available to all projects.<br>
</div>
2. Populate the custom field with all existing Sprint values<br>
<div>3. We then port the existing historic sprint issues to the
correct custom field which preserves all past sprints.<br>
</div>
<div>4. Clear the milestone for all isues on <a href="http://plan.io" target="_blank">plan.io</a><br>
</div>
<div>5. Delete the old, unused milestones<br>
</div>
<div>6. enjoy<br>
<br>
</div>
<div>At least one issue at the upcoming sprint planning meeting
won't be able to be added because of this so I'm hoping we can
resolve in the next few days.<br>
</div>
<div><br>
[0]: <a href="https://pulp.plan.io/versions/50" target="_blank">https://pulp.plan.io/versions/<wbr>50</a><br>
<br>
</div>
<div>Thanks!<br>
</div>
<div>Brian<br>
</div>
</div>
<br>
<fieldset class="m_-6615441638576296832mimeAttachmentHeader"></fieldset>
<br>
</div></div><span class=""><pre>______________________________<wbr>_________________
Pulp-dev mailing list
<a class="m_-6615441638576296832moz-txt-link-abbreviated" href="mailto:Pulp-dev@redhat.com" target="_blank">Pulp-dev@redhat.com</a>
<a class="m_-6615441638576296832moz-txt-link-freetext" href="https://www.redhat.com/mailman/listinfo/pulp-dev" target="_blank">https://www.redhat.com/<wbr>mailman/listinfo/pulp-dev</a>
</pre>
</span></blockquote>
<br>
</div>
<br>______________________________<wbr>_________________<br>
Pulp-dev mailing list<br>
<a href="mailto:Pulp-dev@redhat.com">Pulp-dev@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/pulp-dev" rel="noreferrer" target="_blank">https://www.redhat.com/<wbr>mailman/listinfo/pulp-dev</a><br>
<br></blockquote></div><br></div></div></div></div></div></div>