There should be a means by which bugtrackers whose bugs have been migrated to launchpad can be identified.
Bug #138949 reported by
Graham Binns
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Won't Fix
|
Undecided
|
Unassigned | ||
Bug Description
It's likely that, at some point, there will be several bug trackers whose bugs have been migrated entirely to Launchpad. There should be a means to identify these so that the checkwatches cronscript can automatically discard any bug watches against them.
Revision history for this message
| Gavin Panella (allenap) wrote | #1 |
Revision history for this message
| Gavin Panella (allenap) wrote | #2 |
Revision history for this message
| Graham Binns (gmb) wrote | #3 |
| Changed in malone: | |
| status: | New → Won't Fix |
To post a comment you must log in.
There is another reason for something like this: https:/
It's not really a bug tracker, but was found and auto-created by our bug watch discovery stuff because it uses URLs that match the pattern of Mantis. It would be useful to just say: don't check this. Leave it there so that it doesn't get auto-created again, but in a disabled state.
So a simple "Enabled" checkbox might be enough, with a suggestion to the user that the bug tracker description should be updated to say why. Or, if we want to capture the reason, a radio group:
(*) Enabled.
( ) Disabled: Project has migrated bug tracking to Launchpad Bugs.
( ) Disabled: The remote site is not a bug tracker.
( ) Disabled: By request of the remote site.
( ) Disabled: Other reason.