Bug watches should handle remote private bugs gracefully
Bug #177495 reported by
Graham Binns
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
Low
|
Unassigned | ||
Bug Description
At present, if a bug being watched by Launchpad is private, checkwatches.py will not be able to import that bug's status and importance. We should have a specific BugWatchErrorType, for example PRIVATE_BUG, for this situation so that we can tell the user that we couldn't update the remote bug because the remote bug was private. This is better - or at least more informative - for the user and better for our logs, since private bugs will no longer show up as errors and will be handled by the internal ExternalBugTracker machinery.
| Changed in malone: | |
| status: | New → Confirmed |
| description: | updated |
Revision history for this message
| Graham Binns (gmb) wrote | #1 |
| Changed in malone: | |
| importance: | Undecided → Low |
| status: | Confirmed → Triaged |
To post a comment you must log in.
A PRIVATE_REMOTE_BUG BugWatchErrorType was added in the fix for bug 183737. However, its use is as yet limited to watches against SourceForge-like external bugtrackers.