Old bug watch errors don't get cleared if the remote bug doesn't change
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Triaged
|
Low
|
Unassigned |
Bug Description
What happens:
If a bug watch on a bug tracker on which an LP plugin is installed has failed to update in the past, but has not been changed on the remote system since, the error will never be cleared in Launchpad. This is because Launchpad will check to see if the remote bug has changed and if not won't bother to update the watch.
What should happen:
If Launchpad has an error recorded for a bug watch it should always check that watch, regardless of whether or not the bug has changed on the remote server.
An example of this bug can be found as follows:
Bug 67476 is linked via upstream Metacity to <https:/
Bug 507603 is the same problem with a debbugs instance.
Changed in malone: | |
status: | Incomplete → Triaged |
importance: | Undecided → Low |
tags: | added: cleanup |
tags: |
added: tech-debt removed: cleanup |
This is odd; there's no activity recorded for the bug watch and yet it was apparently updated less than a day ago.
I'll have a poke around with the help of a sysadmin to try and find out what's going on.