"Updating Launchpad bug reference" comment is redundant
Bug #296707 reported by
Matthew Paul Thomas
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Triaged
|
Low
|
Unassigned |
Bug Description
In <http://
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.
To post a comment you must log in.
-----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 getfiregpg. org
importance low
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: http://
iEYEARECAAYFAkk ZkooACgkQwutMq0 2tGPrRbACcDGi6G /EcmPr8vpEBAiKh 472v Z+85CSUK6BptDUC i0
LyAAn2dYuZ3ERHk
=zGFy
-----END PGP SIGNATURE-----