Open Bug 821270 Opened 12 years ago Updated 6 years ago

[Meta] Transition commonly used whiteboard annotations to keywords

Categories

(bugzilla.mozilla.org :: General, task)

Production
task
Not set
normal

Tracking

()

People

(Reporter: emorley, Unassigned)

References

Details

Many groups have started using their own whiteboard annotations for bug grouping, when these would be much more appropriate as keywords - for performance reasons (as well as reducing the chance of typos causing bugs to be overlooked). In the past I remember seeing an export of the most commonly used whiteboard annotations, but for the life of me I can't find the link now. Example candidates off the top of my head (though we should really prioritise by frequency once we have another export): [Memshrink:P1] (and P2, P3, no priority meaning untriaged etc) [qa+] / [qa-] [native-crash] [startupcrash] [buildduty] [good first bug] [WebRTC] (though they have their own component, so why they use the whiteboard as well, who only knows...) [push interrupt] [service interrupt] [sheriff-want] (I was the one who started using this, I'd like to transition it) [re-b2g] [asan]
Depends on: 821276
Depends on: 822743
(In reply to Ed Morley (Away 20th Dec-2nd Jan) [UTC+0; email:edmorley@moco] from comment #0) > Many groups have started using their own whiteboard annotations for bug > grouping, when these would be much more appropriate as keywords - for > performance reasons (as well as reducing the chance of typos causing bugs to > be overlooked). > > In the past I remember seeing an export of the most commonly used whiteboard > annotations, but for the life of me I can't find the link now. > > Example candidates off the top of my head (though we should really > prioritise by frequency once we have another export): > [Memshrink:P1] (and P2, P3, no priority meaning untriaged etc) New memshrink keyword with the use of the priority field? > [qa+] / [qa-] Will need to be expanded to be more descriptive such as qa-accepted and qa-denied > [native-crash] > [startupcrash] startup-crash > [buildduty] build-duty > [good first bug] good-first-bug > [WebRTC] (though they have their own component, so why they use the > whiteboard as well, who only knows...) > [push interrupt] push-interrupt > [service interrupt] > [sheriff-want] (I was the one who started using this, I'd like to transition > it) > [re-b2g] > [asan] These would be confusing to those other than the ones who understand their special meaning. Of course we would need to get sign off from the different groups individually before we create the new keywords and possibly migrate them over. We can run a query to see which products/components have the whiteboard values set to get an idea on who to talk to about transitioning them over. dkl
Component: Administration → General
Type: defect → task
You need to log in before you can comment on or make changes to this bug.