[Pulp-dev] Migrating Sprint to Custom Field [happening tomorrow]
bbouters at redhat.com
Tue Mar 6 22:04:24 UTC 2018
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.
On Mon, Mar 5, 2018 at 12:43 PM, Jeff Ortel <jortel at redhat.com> wrote:
> On 03/02/2018 04:17 PM, Brian Bouterse wrote:
> Redmine's milestone feature allows for roadmap pages to be published for
> each project on pulp.plan.io like this one . 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
> 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.
> 2. Any project that does use milestones can't have issues associated with
> milestones also on a sprint. Like pulp_rpm pulp3 issues .
> I'm interested in hearing any solution on resolving these issues, but I
> also have one to share:
> 1. We could create a custom field called 'Sprint' and make that available
> to all projects.
> 2. Populate the custom field with all existing Sprint values
> 3. We then port the existing historic sprint issues to the correct custom
> field which preserves all past sprints.
> 4. Clear the milestone for all isues on plan.io
> 5. Delete the old, unused milestones
> 6. enjoy
> 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
> : https://pulp.plan.io/versions/50
> Pulp-dev mailing listPulp-dev at redhat.comhttps://www.redhat.com/mailman/listinfo/pulp-dev
> Pulp-dev mailing list
> Pulp-dev at redhat.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pulp-dev