Launchpad will only push bug comments to remote bugs that have changed on the remote server

Bug #264642 reported by Graham Binns
2
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
High
Graham Binns

Bug Description

Because of the way that checkwatches works, comments will only be synced for remote bugs that have changed on the remote server.

That isn't a problem for importing comments, since adding a comment qualifies as a change to the bug as far as the plugin APIs are concerned, but for pushing comments it means that bugs submitted in Launchpad in reply to comments on the remote tracker won't be pushed up to the remote tracker until the remote bug itself gets changed for some reason (either with a new comment or with a status change).

Comment pushing (better yet, comment syncing as a whole) should therefore operate differently from the standard checkwatches only-sync-if-changed functionality.

Graham Binns (gmb)
Changed in malone:
assignee: nobody → gmb
importance: Undecided → High
milestone: none → 2.1.9
status: New → Triaged
Graham Binns (gmb)
Changed in malone:
milestone: 2.1.9 → 2.1.10
Graham Binns (gmb)
Changed in malone:
milestone: 2.1.10 → 2.1.11
Revision history for this message
Graham Binns (gmb) wrote :

Whoops; forgot to mark this In Progress.

Changed in malone:
status: Triaged → In Progress
Changed in malone:
milestone: 2.1.11 → 2.1.12
Revision history for this message
Graham Binns (gmb) wrote :

Landed in r7426.

Changed in malone:
status: In Progress → Fix Committed
Graham Binns (gmb)
Changed in malone:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.