New bug link should default to the component of the currently viewed bug.

NEW
Unassigned

Status

()

Bugzilla
User Interface
--
enhancement
4 years ago
4 years ago

People

(Reporter: jgraham, Unassigned)

Tracking

Details

(Reporter)

Description

4 years ago
If I am creating a set of bugs it's likely that they're all in the same component. It would be great if the new bug link on bug pages would default to the component of the current bug to avoid lots of tedious retyping of the component.

Comment 1

4 years ago
(In reply to James Graham [:jgraham] from comment #0)
> It would be great if the new bug link on bug pages

Where is that exactly?

> to avoid lots of tedious retyping of the component.

Erm, typing? It's one click to choose a component from the list.


"would be great" --> severity=enhancement.
Severity: normal → enhancement
(Reporter)

Comment 2

4 years ago
(In reply to Andre Klapper from comment #1)
> (In reply to James Graham [:jgraham] from comment #0)
> > It would be great if the new bug link on bug pages
> 
> Where is that exactly?

The link marked "new" in the header and footer.

> > to avoid lots of tedious retyping of the component.
> 
> Erm, typing? It's one click to choose a component from the list.

Typing on bugzila.mozilla.org. On other installs it seems to be even worse since you have to first scan a list of links to find the right product and then enter a component.

> "would be great" --> severity=enhancement.

Sure, I agree it's an enhancement. It's also an area where bugzilla is more annoying than e.g. Jira, which makes this workflow better by having more useful defaults.

Comment 3

4 years ago
(In reply to James Graham [:jgraham] from comment #2)
> The link marked "new" in the header and footer.

Still not sure *when* (criteria?) exactly that "New" link should remember the last product (?) and/or (?) component, plus not convinced at all that this inconsistency is good.
(Reporter)

Comment 4

4 years ago
Well I agree that careful analysis of the use cases / workflows is needed to make the UI as smooth as possible. Some scenarios in which this behaviour seems more useful:

1) I am filing a number of bugs in the same component. After filing the first bug, I don't want to re-enter all the common information for the second bug.

2) I am viewing a bug to check if it's the same bug I have found. I decide it isn't and file a new bug instead. In this case the bug I'm filing is most likely in the same component as the one I was just viewing.

3) I'm viewing a query that has selected bugs all from a specific component. Evidently I'm working on that component (maybe the query is to check for dupes) and so the next bug I file is likely to be in the same component.

Obviously any change here is likely to reduce the consistency compared to forcing every interaction through the top-level bug filing UI on the homepage. But consistency isn't the only hallmark of good design. In this case we are ignoring contextual data that would make common workflows much smoother, without making other workflows impossible or even more difficult.
You need to log in before you can comment on or make changes to this bug.