Launchpad itself

Bug reports aren't easily distinguishable in Web search results

Bug #128462 reported by Sitsofe Wheeler on 2007-07-26

Affects		Status	Importance	Assigned to	Milestone
	Launchpad itself	Triaged	Low	Unassigned

Bug Description

Bug titles in launchpad have to start with "Bug #XXX". The problem is that the information that differentiates bugs is not first which leads to drawbacks when things do truncation. A good example of when this is when I use Google (which is useful because it is very fast, its full text search often finds more than Launchpad's and it has a cache) to search Launchpad bugs, e.g. http://www.google.co.uk/search?hl=en&client=firefox-a&rls=com.ubuntu:en-US:official&hs=mzc&q=+site:bugs.launchpad.net+launchpad+nvidia+edid

See original description

Tags:

Revision history for this message

Matthew Paul Thomas (mpt) wrote on 2007-08-01:

That's an interesting problem.

I'm not keen on putting the bug number anywhere other than the beginning, because it has a high usefulness-to-length ratio. (When I have open half a dozen bug reports, it's useful to see their numbers in the window list.)

However, we could remove the "#", and put the name of the affected software after the description rather than before. So instead of
------------
Bug #91292 in linux-restricted-modules-2.6.20 (Ubuntu): “[nvidia-glx] Resolutions lost on upgrade from Edgy to Feisty [nvidia-glx-legacy][nvidia-glx-new]”
------------
we could have
------------
Bug 91292: “[nvidia-glx] Resolutions lost on upgrade from Edgy to Feisty [nvidia-glx-legacy][nvidia-glx-new]” in linux-restricted-modules-2.6.20 (Ubuntu)
------------

description:

updated

Revision history for this message

Sitsofe Wheeler (sitsofe) wrote on 2007-08-02:

Hmm. I've just opened a window with 6 tabs and I see what you mean. However with 12 all I can see is "Bug...".

I like your suggestion but in the interests of space I want to trade your Bug for a # so:
------------
#91292: “[nvidia-glx] Resolutions lost on upgrade from Edgy to Feisty [nvidia-glx-legacy][nvidia-glx-new]” in linux-restricted-modules-2.6.20 (Ubuntu)
------------

This still provides grouping but we get a few more characters. The "" are unfortunate but do make the title clear. I think the only way they could be disposed is if you did something like:
------------
#91292: [nvidia-glx] Resolutions lost on upgrade from Edgy to Feisty [nvidia-glx-legacy][nvidia-glx-new] — linux-restricted-modules-2.6.20 (Ubuntu)
------------

it's easy to play with the ending and introduce parenthesis instead of dashes and so on.

description:

updated

Revision history for this message

Matthew Paul Thomas (mpt) wrote on 2008-03-17:

In <http://bugzilla.gnome.org/show_bug.cgi?id=99604> I described a way to fix this problem in Gnome's window listing.

Changed in malone:
importance:	Undecided → Low
status:	New → Confirmed

Revision history for this message

Sitsofe Wheeler (sitsofe) wrote on 2008-04-07:

mpt:
I'm not sure that helps in the Google search listing case though...

Revision history for this message

Martin Pool (mbp) wrote on 2009-09-01:

See also bug 419557 that this affect's Launchpad's internal free-text search.

> However, we could remove the "#", and put the name of the affected software after the description rather than before.

That sounds good to me, especially now that Launchpad is more relaxed about which pillar you use to reach a bug. The fact that you're looking at it in the context of a particular product is fairly uninteresting, and the description probably gives you a good clue.

Maybe less so for bugs like "crashes in g_object_foo", but I think it's still worth trying.