even when a project has an external bug tracker, bug references are always linkified within LP

So it seems to me this is not mysql-specific but rather a general issue that "bug #1234" in commit messages may refer to upstream bug numbers, not Launchpad bugs?

Yes, it probably applies to many other projects. One idea is to store a format string that would be used to form the link to the bug tracker, probably in the same table that we store a link to the upstream bugtracker.

On Fri, May 30, 2008 at 02:52:42AM -0000, Elliot Murphy wrote:
> Yes, it probably applies to many other projects. One idea is to store a
> format string that would be used to form the link to the bug tracker,
> probably in the same table that we store a link to the upstream
> bugtracker.

We kind of have this already in the code. Are you referring to something
that could be set manually, or simply a cache, so that you wouldn't have
to get the bug tracker from the db?

    subscribe

I was thinking of something that could be used by the text-to-html formatter, which currently has a hard coded format string. It makes sense that the bug watch code would already be storing a format string for the upstream tracker, so it's just a question of hooking that up to text-to-html.

On Saturday 31 May 2008 02:19:38 Elliot Murphy wrote:
> I was thinking of something that could be used by the text-to-html
> formatter, which currently has a hard coded format string. It makes
> sense that the bug watch code would already be storing a format string
> for the upstream tracker, so it's just a question of hooking that up to
> text-to-html.

This is exactly what I was thinking too.

Something like an additional path to text-to-html to specify project
bug links or something.

This seems more like a Bugs issue than a Code issue.

On Tue, Jul 08, 2008 at 08:02:31AM -0000, Jonathan Lange wrote:
> This seems more like a Bugs issue than a Code issue.
>
> ** Changed in: malone
> Product: Launchpad Bazaar Integration => Launchpad Bugs

Not really. To fix this you'd have to do something special when
rendering the commit messages, so I think the ultimate responsibility
lies on the Code team.

OK. Still probably a good thing to talk with Bugs about though :)

I don't see why the Code team would need to do something special. We're using a standard formatter. If the project's bug settings indicate that they use a different tracker, that formatter could automatically link to that tracker.

On Mon, Apr 26, 2010 at 08:12:31PM -0000, Aaron Bentley wrote:
> I don't see why the Code team would need to do something special. We're
> using a standard formatter. If the project's bug settings indicate that
> they use a different tracker, that formatter could automatically link to
> that tracker.

Well, you're using a standard formatter that has access only to a text
string. It doesn't know in which context it is.

You would have to either extend the existing one, or create a new one,
and pass in the project the bug ids should link to.

--
Björn Tillenius | https://launchpad.net/~bjornt

See also bug 712059 which is about the same issue in the context of federated bug comments.

I'm going to rephrase this as 'even when a project has an external bug tracker, bug references are always linkified within LP.' This suggests a reasonable first approximation: use the tracker that most of the contexts use when linkifying bug text. For code there will always be one context, for bug comments there may be many (and we don't [currently] record the originating context, so we would inherit the bug context).

This would be nice to have but isn't a killer facility at the moment, would love patches (and be happy to mentor) - but dropping to low from a project perspective for now.