"Also affects project" not obvious for upstream bug links

Bug #294270 reported by EmmaJane on 2008-11-05
4
Affects Status Importance Assigned to Milestone
Launchpad itself
Low
Unassigned

Bug Description

The link "Also affects project" is not obviously the place to add the URL for a bug report for the upstream project. Please add a title attribute (or use some other technique) to explicitly state, "Add URL for upstream bug project here."

Martin Albisetti (beuno) wrote :

Very true!

Changed in launchpad:
importance: Undecided → Medium
status: New → Triaged
Bryce Harrington (bryce) on 2010-06-23
tags: added: better-forwarding trivial
huwshimi (huwshimi) on 2011-03-28
tags: added: ui-easy
tags: added: easy
removed: ui-easy
Chris Johnston (cjohnston) wrote :

Is the title attribute the way we would like to go, or change the wording on the page?

Curtis Hovey (sinzui) wrote :

We intend to change the also-affect use-cases. They are legitimate to add a bug task, but most cases users want to retartget, which is not supported. We intend to support retargeting in the next few months. Most users do not know what "upstream" or "downstream" is. We have had to remove those words, or explain them in detail. Consider that this link is also shown on projects and the bug may not actually be upstream or downstream. The user really is adding a project or distro+sourcepackage bug task, not an upstream/downstream task.

The link rendering code supports titles attributes. You can pass the 'summary' kwarg to the Link() contructor to provide a title attribute. The 'addupstream' method of BugContextMenu in lib/lp/bugs/browser/bugs.py needs the summary. Actually, most of the link in the menu appear to be missing the summary attribute :(

Curtis Hovey (sinzui) on 2011-09-27
Changed in launchpad:
importance: Medium → Low
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers