Launchpad itself

Viewing a bug in the wrong context should allow user to jump to one of the right contexts

Bug #141215 reported by Matthew Revell
8
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Low
Unassigned

Bug Description

When viewing a bug in a context against which it has not been reported, there's no easy way to jump to the right context.

For example: if I view a malone bug in the rosetta context, Launchpad tells me that the bug isn't reported against rosetta but Launchpad doesn't tell me which context(s) the bug is reported in, nor does it provide a way in the interface to jump to one of those correct contexts.

Example: https://bugs.edge.launchpad.net/launchpad-bazaar/+bug/117055

See also bug 87233.

See original description
Revision history for this message
Francis J. Lacoste (flacoste) wrote :

The list of contexts in which the bug is reported is displayed in the normal table. You can jump to one of those contexts by clicking on the context name.

I notice though that the 'Affects' table is grayed out when the bug is displayed out-of-context, maybe that's what made you not see it?

Changed in malone:
status: New → Incomplete
Revision history for this message
Matthew Paul Thomas (mpt) wrote :

The table is not greyed out when the bug report is displayed out-of-context, it is greyed out only when the report is a duplicate. You may be confusing the lack of any highlighted row (which would normally emphasize which context you were in) as greying out.

Low importance because the situation is only an irritant. As far as I can tell, there is nothing you are prevented from doing by being in the wrong context: you just get the wrong headings.

Changed in malone:
importance: Undecided → Low
status: Incomplete → Confirmed
Revision history for this message
Matthew Paul Thomas (mpt) wrote :

Actually, if bug 134220 is fixed by restoring the details box as it was originally, *that* will be something you are prevented from seeing by being in the wrong context.

Matthew Paul Thomas (mpt)
description: updated
Revision history for this message
Brian Murray (brian-murray) wrote :

With bug reports about Ubuntu packages if you view a bug report in the wrong context the "source package" portlet becomes almost useless. It would be better if you change the context without have to hack the url.

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

If bug 152878 and bug 246041 are fixed, I think there will no longer be any point in fixing this bug.

William Grant (wgrant)
Changed in launchpad:
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Related blueprints

Remote bug watches

Bug watches keep track of this bug in other bug trackers.