Changing the Project a bug report is for causes the Further Information dialog to be removed

Bug #723509 reported by Terry Jones on 2011-02-23
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Low
Unassigned

Bug Description

When I go to report a bug on something in Launchpad that has several Projects, I am first asked to write a Summary of the bug. If I do this and click Next, a textarea is displayed that lets me enter Further Information. So I go to the Further Information area and type in a nice long bug report.

I then realize that I didn't select the right Project from the the multiple-choice Project drop-down above the Summary area. So I pick the correct project and..... poof! The Further Details textarea widget is blown away, along with my carefully written bug report and so I have to write it all again (and file a bug on Launchpad :-)).

Thanks!

Curtis Hovey (sinzui) wrote :

There is a fundamental flaw in this use case that makes this low instead of high. Most users cannot choose the correct project in a group of projects. Only those affiliated the project can place the bug in the correct project. Launchpad should not make someone choose the project. It does because project groups cannot have bug (or questions or branches). This can be fixed by abandoning project groups...nested project solves a lot of usability and community issues. nested projects would make this bug invalid.

Changed in launchpad:
status: New → Triaged
importance: Undecided → Low
tags: added: confusing-ui dupefinder projectgroups

While I agree that /many/ bugs filed in the context of a group can
only be properly assigned by folk fluent with the code, there are
often many folk fluent with the code. Even with project groups moved
to a looser affiliation, I imagine we'll still want a mechanism for
people to file a bug where they don't know the specific project
a-priori.

That said, this certainly is not a regression, its been naffed for a
long time, and we have only a few project groups. When we work on the
project group aspect this bug will likely be picked up and worked on.

Jamu Kakar (jkakar) wrote :

I'd like to second Robert's comment... I almost always know which
project I want to file a bug about. Any solution to improve the
situation for bug reporters that don't know where to file a bug
shouldn't make it harder for me to file a bug. I would guess that, in
the general case, random Ubuntu users reporting bugs won't have enough
information to make such decisions, but that people involved in
upstream projects will.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers