"Updating Launchpad bug reference" comment is redundant

Bug #296707 reported by Matthew Paul Thomas
2
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug Description

In <http://gobby.0x539.de/trac/ticket/271>, the last action is the Launchpad Trac plug-in updating the Launchpad bug reference. This is followed by a comment: "Updating Launchpad bug reference". This comment has then been imported into <http://launchpad.net/bugs/70653>, where it's not relevant to anyone using Launchpad.

If the Launchpad Trac plug-in just changed the bug reference without an extra comment, it would still be obvious in Trac (because it would still say "launchpad_bug set to 70653"), but there would be no redundant comment imported into Launchpad.

Tags: lp-bugs
Revision history for this message
Graham Binns (gmb) wrote : Re: [Bug 296707] [NEW] "Updating Launchpad bug reference" comment is redundant

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> If the Launchpad Trac plug-in just changed the bug reference without an
> extra comment, it would still be obvious in Trac (because it would still
> say "launchpad_bug set to 70653"), but there would be no redundant
> comment imported into Launchpad.
>

Unfortunately, that's the way that bug metadata updates are handled in
Trac; every transition becomes a comment; there's no way to turn this
off, AFAICT.

The only way to avoid these comments appearing in Launchpad, then, is
to explicitly filter them out. This shouldn't be too hard to do since
the user who authored the comment should be the 'launchpad' user
(unless someone's done some customisation of the plugin, in which case
all bets are off).

 status triaged
 importance low
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: http://getfiregpg.org

iEYEARECAAYFAkkZkooACgkQwutMq02tGPrRbACcDGi6G/EcmPr8vpEBAiKh472v
LyAAn2dYuZ3ERHkZ+85CSUK6BptDUCi0
=zGFy
-----END PGP SIGNATURE-----

Changed in malone:
importance: Undecided → Low
status: New → Triaged
Revision history for this message
Graham Binns (gmb) wrote :

However, this behaviour is part of the cause of bug 296789.

Revision history for this message
Matthew Paul Thomas (mpt) wrote :

<http://gobby.0x539.de/trac/ticket/272> and <http://gobby.0x539.de/trac/ticket/273>, to pick just the first two examples I looked at, include status changes that seem not to be accompanied by comments. In the former, "* type changed from defect to enhancement". And in the latter, "* status changed from new to closed * resolution set to wontfix".

Are these lines actually injected as comments in Trac markup, so it's impossible to distinguish them from real comments?

Revision history for this message
Graham Binns (gmb) wrote :

Herb has now deleted the offending comments and watches from this bug. Hurrah.

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.