1345575 - Collapsed "Status" area should show bug component

Status: RESOLVED FIXED

(bugzilla.mozilla.org :: User Interface, enhancement, P3)

Description

[Bill McCloskey [inactive unless it's an emergency] (:billm)]

The component is, for me, one of the most important aspects of a bug. If a bug ends up in the wrong component, it can very easily be lost forever.

It would be really nice if the collapsed text for the "Status" line said something like "NEW Core::DOM bug which should be worked on in the next release/iteration" instead of just "NEW bug which should be worked on in the next release/iteration".

Comment 1

[Emma Humphries ☕️🎸🧞‍♀️✨ (she/they) [:emceeaich] (Pacific Time) use needinfo]

Created https://github.com/mozilla/bugzilla-readable-status/issues/24. PRs with updated tests are always welcome!

Comment 2

[:glob ✱]

is this really necessary with the component visible just below the summary?
i'd also be concerned about long component names, and their impact on the ability to quickly scan the status summary.

bill - perhaps you could expand the status block, and leave it open.  then the component will always be visible.

Comment 3

[Bill McCloskey [inactive unless it's an emergency] (:billm)]

(In reply to Byron Jones ‹:glob› from comment #2)
> is this really necessary with the component visible just below the summary?

The only thing I see below the summary is "NEW" and "Unassigned". (Both of which, I might add, are shown elsewhere in the UI!)

> i'd also be concerned about long component names, and their impact on the
> ability to quickly scan the status summary.

In most cases, the component name isn't very long. We should be optimizing for the common case.

> bill - perhaps you could expand the status block, and leave it open.  then
> the component will always be visible.

Yeah, but that's a waste space. Everything I want fits on one line.

Comment 4

[:glob ✱]

(In reply to Bill McCloskey (:billm) from comment #3)
> > is this really necessary with the component visible just below the summary?
> 
> The only thing I see below the summary is "NEW" and "Unassigned". (Both of
> which, I might add, are shown elsewhere in the UI!)

oh, you're talking about the summary at the top of the page, not the 'readable bug status' blurb.
the intent of that block is to provide an quick summary of the _state_ of the bug, not to just replicate important fields.

if the scope of that is expanded determining what metadata to add to it is difficult as different roles/teams/people have different requirements with regards to what is important.

> > bill - perhaps you could expand the status block, and leave it open.  then
> > the component will always be visible.
> 
> Yeah, but that's a waste space. Everything I want fits on one line.

i'll leave the decision with the bmo team, but to me this is a wontfix.

Comment 5

[Bill McCloskey [inactive unless it's an emergency] (:billm)]

(In reply to Byron Jones ‹:glob› from comment #4)
> (In reply to Bill McCloskey (:billm) from comment #3)
> > > is this really necessary with the component visible just below the summary?
> > 
> > The only thing I see below the summary is "NEW" and "Unassigned". (Both of
> > which, I might add, are shown elsewhere in the UI!)
> 
> oh, you're talking about the summary at the top of the page, not the
> 'readable bug status' blurb.

No, I was talking about the status blurb. I thought you were talking about the summary at the top of the page. In any case, I was just pointing out that there's a lot of redundancy there. If we only showed the bug status and assignee fields once, then there would be more space for the component.

Comment 6

[Kohei Yoshino [:kohei]]

The fix is already in my pull request for Bug 1344091.

Comment 7

[Kohei Yoshino [:kohei]]

Fixed in Bug 1344091.