[openstack-dev] [Launchpad] Fwd: How to correctly change the bug milestone...
tsufiev at mirantis.com
Wed Apr 8 15:36:50 UTC 2015
The mail being forwarded was originally intended for MIrantis internal
mailing list, but then I've realized that it fits as well to the general
Openstack mailing list.
---------- Forwarded message ----------
From: Timur Sufiev <tsufiev at mirantis.com>
Date: Wed, Apr 8, 2015 at 6:22 PM
Subject: How to correctly change the bug milestone...
To: mos-dev <mos-dev at mirantis.com>
... or why we shouldn't use Launchpad at all
Recently thanks to our new LP reports tool I've discovered that we "lost" 3
bugs in MOS Horizon. Well, they weren't actually deleted, instead they were
set to "Won't fix" in the Milestone/Series they were originally filed to.
I've decided to find out what it takes to correctly change the bug
milestone to not lose it. Here is the absolute minimum of steps tested on
~10 bugs I've just moved from 6.1 milestone to 7.0.
1. Nominate the bug for series 7.0 (and make sure it's also nominated for
2. Change status in 6.1 to "Won't fix"
3. Refresh the page (it's important!)
4. Observe the new link in the rightmost column of the top row in a list of
affected series - 'Mirantis Openstack 6.1' and change it to 'Mirantis
5. Repeat for whatever number of bugs you have for the milestone that's
almost soft code-freezed.
That's it! Now, you will see all the bugs (in my case, with 'horizon' tag,
query https://bugs.launchpad.net/mos/+bugs?field.tag=horizon) in the
standard Launchpad view, which wouldn't be the case if they were still
tracked as of 'Mirantis Openstack 6.1' series which got "Won't Fix" status.
Of course, you could also use LP Reports tool, but it's still slower than
native LP UI due to a larger number of calls it makes.
And frankly speaking, I'm eager to see Storyboard project ready to finally
move away from this sordid piece of software called 'Launchpad'.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev