Feature Request P3
Status Update
No update yet.
Comments
ma...@gmail.com
[Description Changed]
xt...@gmail.com
[Comment Deleted]
ek...@google.com
[Empty comment from Monorail migration]
ek...@google.com
[Empty comment from Monorail migration]
na...@codeaurora.org
[Empty comment from Monorail migration]
na...@codeaurora.org
[Empty comment from Monorail migration]
ek...@google.com
Looks like using a required field for tracking the version is currently not feasible with Monorail:
https://bugs.chromium.org/p/monorail/issues/detail?id=10106#c2
na...@codeaurora.org
Looks like chromium will be moving to buganizer and we'll probably do that as well. We can keep this ticket open until then.
ek...@google.com
[Empty comment from Monorail migration]
is...@google.com
Edits were made to reflect the following in Monorail: auto-CCs.
ma...@gmail.com
as a first step
- find out if we use "Version" of "Found In" field
- fill in existing release versions
- make the field mandatory
ek...@google.com
Sorry, I don't find time looking into this, hence unassigning.
Description
Gerrit Bug Triaging & Issue Management at the virtual user summit in June 2021
Have a field tracking the affected release
- Auto-closes issues for not supported version with comment
- Saying it can be reopened if it can be reproduced on a newer version
- Pointing to the SLO documentation
- Exclude recently updated issues from auto-closing, so that people can at least discuss for old versions