All triage owners should be in the group granting access to the Rank field

NEW
Unassigned

Status

()

bugzilla.mozilla.org
Bug Creation/Editing
a year ago
a year ago

People

(Reporter: emceeaich, Unassigned)

Tracking

Production

Details

Rank is useful in structuring the piles of backlogged bugs. Rank is currently a restricted access field. 

Let's grant rank to triage owners, and if that is too difficult, can we grant it to editbugs, and if not, then just make it open and we can monitor how it's being used.
(In reply to Emma Humphries ☕️ (she/her) [:emceeaich] (UTC-8) +needinfo me from comment #0)
> Rank is useful in structuring the piles of backlogged bugs.

Do you have any evidence that it adds value over the priority field? I've yet to be convinced that the granularity it provides adds value and if the priority field doesn't provide enough granularity then the Rank field should *replace* the priority field or more levels should be added to the priority field since they're both about prioritization from what I've seen.

> Rank is currently a restricted access field. 
> 
> Let's grant rank to triage owners, and if that is too difficult, can we
> grant it to editbugs, and if not, then just make it open and we can monitor
> how it's being used.

I really don't think it's a good idea to role this out wider without a definition of how it should be used or we're likely to repeat the same problems as before (e.g. for priority, target milestone, votes, etc.) where components use it differently which means reports/queries spanning components and cross-component-projects aren't useful and it adds noise/complexities for everyone.
(In reply to Matthew N. [:MattN] (behind on bugmail; PM if requests are blocking you) from comment #1)
> (In reply to Emma Humphries ☕️ (she/her) [:emceeaich] (UTC-8) +needinfo me
> from comment #0)
> > Rank is useful in structuring the piles of backlogged bugs.
> 
> Do you have any evidence that it adds value over the priority field? 

Several components (Audio/Video) are already using it to structure their backlogs. 

Graphics would also be interested in using it to provide direction.


> I really don't think it's a good idea to role this out wider without a
> definition of how it should be used or we're likely to repeat the same
> problems as before (e.g. for priority, target milestone, votes, etc.) where
> components use it differently which means reports/queries spanning
> components and cross-component-projects aren't useful and it adds
> noise/complexities for everyone.

Yes, this would need to happen with documentation if we open it generally, but I'm hoping it's easier just do limit who we expose the field to. 

If we're willing to take on work, we could further limit how rank works such that it only becomes editable if the user is in the proper group *and* the priority field is P2, or P3, or just P3.
You need to log in before you can comment on or make changes to this bug.