Excerpts from Jeremy Stanley's message of 2018-01-16 16:29:32 +0000: > On 2018-01-16 06:55:03 -0800 (-0800), Emilien Macchi wrote: > [...] > > I created a dev instance of storyboard and imported all bugs from > > TripleO so we could have a look at how it would be if we were using > > the tool: > [...] > > Awesome! We do also have a https://storyboard-dev.openstack.org/ > deployment we can do test migrations into if you'd prefer something > more central with which to play around. > > > - how do we deal milestones in stories and also how can we have a > > dashboard with an overview per milestone (useful for PTL + TripleO > > release managers). > > So far, the general suggestion for stuff like this is to settle on a > consistent set of story tags to apply. It really depends on whether > you're trying to track this at a story or task level (there is no > per-task tagging implemented yet at any rate). I could imagine, for > example, setting something like tripleo-r2 as a tag on stories whose > TripleO deliverable tasks are targeting Rocky milestone #2, and then > you could have an automatic board with stories matching that tag and > lanes based on the story status.
That sounds like it might also be a useful way to approach the goal tracking. Can someone point me to an example of how to set up an automatic board like that? Doug __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev