Example:
QA engineer finds a bug in 5.0.1 (5.0.x series), which is milestone for stable/5.0 branch, and current development (master) is 5.1 milestone (5.1.x series).
According to our latest Fuel discussions, we need to automate auto-proposal for development milestone (5.1) to avoid possible loss of bugs in development version, while it is going to be fixed in stable branch.
To generalize it even more, I request to make such a script which will be "affecting" (in terms of LP) development milestone for any new bug, which would be created and targeting milestone which is older than development (for example, 4.1.2, 5.0.1 should affect 5.1).
There is no need to check all bugs in the past, and I assume that script will have such a logic that it will start doing this only for new bugs, starting from the moment of script run.
Then for developers / bug team, if bug doesn't really affect development milestone and affects only what it was proposed for, then it should be marked as "Invalid" or "Won't fix" for development milestone, with corresponding comment in the LP bug.
Original purpose of this script was extended to also go over all Critical bugs in current development milestone and target maintenance milestone. Like if you have 6.1 Critical, it will target 6.0.1. Also, it does the same thing for all customer-found tagged bugs. It's being discussed with sustaining team if we want to target all ".*-updates" milestones of such 6.1 Critical & customer-found.
Dmitry, as I remember you had write some launchpad scripts. What they able to do?
Thanks.