Add a script to set the remote_product for projects linked to external bug trackers
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
High
|
Björn Tillenius |
Bug Description
Once bug #300686 is fixed it will be possible for Launchpad to record the remote product of a project. However, rather than make the project maintainers go and update the remote product in order for Launchpad to be able to use it, we can can use existing bug watches to automatically populate the remote_product field.
We should add a script that sets the remote_product for a Product by using the existing ExternalBugTracker and BugWatch infrastructure to get the remote product from the remote bugtracker.
Obviously this is a bit error prone, since it's possible to link to a bug on a bug tracker that tracks multiple projects without the bug being on the relevant remote product for the project in Launchpad. In order to make this a bit more bulletproof, we could add another step of error checking into the script:
* Before setting the remote_product, check to see if other bug watches for the same Product contain conflicting remote product data and only set remote_product if the data are consistent.
Changed in malone: | |
milestone: | none → 2.2.2 |
description: | updated |
Changed in malone: | |
assignee: | nobody → bjornt |
importance: | Undecided → High |
status: | New → In Progress |
Changed in malone: | |
status: | Fix Committed → Fix Released |
Fixed in RF7811