Issue metadata
Sign in to add a comment
|
[Label Request] Hotlist-Reassess-2018 |
||||||||||||||||||||||
Issue description1] Label Name: Hotlist-Reassess-2018 2] Parent Label (e.g. Proj-, Hotlist-, etc...): Hotlist 3] Description of Label: Pri-3 bug that can ignored until 2018 Long description: This label is for priority-3 bugs that are somehow less important than other priority-3 bugs. These are bugs we’re sure no one on the team intends to fix this year (e.g., really unimportant, or mostly unimportant and hard to fix, especially given current engineering headcount / constraints). 4] Please specify what triage practices will be followed for the label (i.e. what team will do it and how frequently). Only bugs that are triaged should have this label applied to them. Thus, no triage practices are necessary. It is expected that teams who take advantage of this label will do a one-pass triage process in the beginning of 2018. If this label helps our and other teams' workflow, I fully expect to create a Hotlist-Reassess-2019 label early next year.
,
Apr 14 2017
CC laforge@google.com, in hopes that this will be acted upon. This label is definitely proving useful. It would be nice if it was automatically offered in the dropdown so I didn't have to copy and paste each time I wanted to apply it. (I do that so I don't end up with typos in the label name.)
,
Apr 19 2017
Now that we officially have Hotlists supported in crbug.com (under profile), we are recommending that teams use them over labels for use cases like these. The give folks more direct control (also add new capabilities like order and notes) and don't require admins to create labels.
,
Apr 19 2017
I don't think that works for this use case. The primary use of this is searching, i.e., find in a particular component all bugs that are (or--especially--aren't) on the hotlist. As far as I can tell, monorail's personal hotlist support does not provide this functionality.
,
Apr 19 2017
+Jason to answer the question about query support.
,
Apr 28 2017
Please add this hotlist to the dropdown so I don't have to continually copy-and-paste it.
,
Apr 28 2017
I am tracking the implementation of searching by hotlist in issue monorail:2083 . I won't get to it in the next 2 weeks, but probably not too long after that.
,
May 2 2017
laforge@: even if searching by hotlists works, I think this is a generally useful label, not particular to a team. I can see it being widely used in the same way Hotlist-Polish or Performance-Browser is. Hence, I think it should appear to everyone in the label suggest dropdown, which personal/team hotlists do not.
,
May 2 2017
So one quick thought. If I'm understanding the usage of this label correctly, it is effectively a check in date to say look at me in 2018. It seems like the "NextAction" date, which is attached to every issue (and can be queried on for presence/ absence/ and explicitly used in ranged queries), is analogous to what's being described, but affords more generalized usage/ behavior. Could we simply use (and recommend) that instead?
,
May 9 2017
I think the searching abilities for NextAction suffices. I guess we don't need the Hotlist; we just say in a comment "Will reassess next year." and set NextAction appropriately. Thanks for the suggestion. Closing this bug as WontFix.
,
May 9 2017
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by mpear...@chromium.org
, Mar 30 2017