no direct link from bug comment page to corresponding bug

[André Rüdiger]

I hope I'm not missing something but it's more complicated than necessary to navigate from a comment page to the corresponding bug page.

Steps to reproduce:
1. click on a link to a bug comment (i.e. https://launchpad.net/ubuntu/+source/hal/+bug/66068/comments/13)
2. try to navigate to the corresponding bug report
3. fail

Workaround:
- remove /comments/[comment#] from url

Solution:
- make the bug title on top of the comment page a link to the bug

[André Rüdiger (andreruediger-deactivatedaccount)]

Ok, I missed the link in the bug details. Anyway, I think the solution proposed above should work better.

Thanks.

[Tim Penhey (thumper)]

If there was a bug details portlet, it has gone now.

I was given the link https://bugs.launchpad.net/launchpad-bazaar/+bug/53340/comments/20 and wanted to see the entire bug report, and was mildly surprised when I couldn't find a link back to the bug itself.

In the edit details page, the Bug #XXXX is a link to the main bug report, and I think we should have that consistency on the comment page itself.

[era (era)]

Pretty please, this should not be at all hard to do, probably a one-line change, and it would add consistency with other similar pages nearby in the hierarchy.

[Martin Pool (mbp)]

This is more serious than you might think because Google sometimes likes to link to individual comment pages, eg

  https://bugs.edge.launchpad.net/bzr/+bug/198793/comments/1

A new user might think this was the entire content of the bug - there is no indication this is just one comment, and no link to the larger context.

[Artem Popov (artfwo)]

Confirming, this is a big issue for me as well.

[Martin Pool (mbp)]

See also bug 181938, the same thing for announcements.

[Carlos Laviola (claviola)]

A fairly obscure workaround to avoid having to edit the URL manually is to click on "Activity Log" on the right sidebar first, since that page does have a link to the full bug report.

[Matthew Revell (matthew.revell)]

I'm changing the project to Launchpad Bugs, rather than Launchpad Foundations.

[Matt Zimmerman (mdz)]

Confirmed, I just saw this again when https://bugs.edge.launchpad.net/ubuntu/+source/xorg-server/+bug/92482/comments/29 turned up in search results.

[Martin Albisetti (beuno)]

Fixed in RF 7293

[Karl Fogel (kfogel)]

Well, this is already fixed, but note that fixing bug #124166 would obviate the need for the fix.

[Jānis Kangarooo (kangarooo)]

Why theres Fix Comited? THis isnt yet fixed.
in coment https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/89860/comments/55
theres navigation Ubuntu “linux-source-2.6.20” package Bugs Bug #89860 but its not clickable. It should be clickable or better make clickable Comment 55 for bug 89860. Make clickable this second part bug 89860.

[Martin Pool (mbp)]

Confirmed, this does seem to have regressed, perhaps because of portlet removal?

[William Grant (wgrant)]

The regression is caused by the recent delinking of the final breadcrumb item.

[Graham Binns (gmb)]

As William said, this is a result of the breadcrumb change. I think it'd make sense to add a breadcrumb for the comment itself.

[William Grant (wgrant)]

It probably also makes sense to adjust the breadcrumb linking logic to verify that the context object and view match before electing to unlink it. Although I'm not sure how feasible that is.

[Graham Binns (gmb)]

That sounds sane, though it's been a long time since I prodded the
breadcrumb code, so I've no idea how feasible it is either.
Definitely worth looking into, though.

[Ursula Junque (ursinha)]

Fixed in stable r10585 <http://bazaar.launchpad.net/~launchpad-pqm/launchpad/stable/revision/10585>

[James Westby (james-w)]

Tested on this bug, it's there, but not particularly obvious as the breadcrumbs
aren't link coloured or underlined, but at least you don't have to URL hack anymore.

Thanks,

James

[Deryck Hodge (deryck)]

Thanks for testing, James!

I agree the breadcrumbs-as-links meme is hampered by not being obvious, so maybe we should file a bug about that. Many users are likely use to this by now, though.

[Martin Pool (mbp)]

I agree with James. I would consider this bug thoroughly fixed when the "bug 78565" in the heading also links to the bug. It's the big obvious thing to click.