- Product group Product Designers are DRI for all stories/bugs that
their group implements
- Rename "Context" to "Resources" in story template. Today, we're using
it for resources
This new `:incoming` label is used by engineers to filter down to _new_
bugs on their sprint board during each standup. They will remove the
label, indicating they have triaged the issue.
QA removes `:reproduce`, EM removes `:incoming`.
Since a lot of bugs end up needing additional product design work, I
propose adding a (commented-out by default) section to this template to
standardize where to add design changes, once settled.
Reasoning: in estimation sessions, it can sometimes be hard to find this
information: sometimes it's in the comments, sometimes it's been added
to the description... either way, its not always obvious to spot. I
think it will help us move quicker if there's a consistent heading to
look for.
(Also, open to suggestions for other ways of wording that heading! This
is just the way I've been adding it to issue descriptions lately.)
Adding addition fields & re-ordering the Bugs template to facilitate
more robust bug reporting.
---------
Co-authored-by: Mike McNeil <mikermcneil@users.noreply.github.com>
- Add a "Fleet tier" and "User role" to specify which tier of Fleet and which role the individual reporting the bug is assigned
- Edit Markdown Link Check GitHub action to run against the `main` branch
- Add 2 sections in `CONTRIBUTING.md` these 2 sections correspond to the "Bug report" and "Report a security vulnerability" issue templates
- Add "Is this an issue with the Fleet UI" to "Bug report" section in `CONTRIBUTING.md`. This includes a walkthrough for opening the browser's JS console and network requests
- Fix misspelled file name
