Plan group issues requiring attention
Heat map for bugs:
| ~S1 | ~S2 | ~S3 | ~S4 | ~"No severity" | |
|---|---|---|---|---|---|
| ~P1 | 0 | 0 | 0 | 0 | 0 |
| ~P2 | 0 | 5 | 2 | 0 | 0 |
| ~P3 | 0 | 1 | 41 | 11 | 0 |
| ~P4 | 0 | 0 | 12 | 14 | 0 |
| ~"No priority" | 0 | 0 | 0 | 0 | 1 |
Hi @ebrinkman,
Here is a list of feature proposals without a milestone.
We would like to ask you to determine whether this issue should be scheduled or closed. For each issue please:
- Close the issue out if it is no longer relevant or a duplicate.
- Assign either a versioned milestone, the %Backlog or the %Awaiting further demand milestone.
For the issues triaged please check off the box in front of the given issue.
Please work with your team to complete the list this week.
-
#12785 (closed) Make epics more accessible/easier to find ~"Plan", UX, devopsplan, feature, ~"group::team planning" -
#12808 (closed) Epic "Tree" tab no longer renders milestones in Issue list ~"Plan", UX, devopsplan, feature, ~"group::portfolio management" -
#12763 (closed) Epic "Tree" tab does not render a tree for epics without sub-epics ~"Plan", UX, devopsplan, epics, feature, ~"group::portfolio management" -
#12762 (closed) Make Tree tab the default view for epics ~"Plan", UX, devopsplan, epics, feature, ~"group::portfolio management" -
#12721 RICE-like scoring system ~"Category::Project Management", ~"Plan", devopsplan, feature, ~"group::team planning" -
#12644 (closed) Add comments and see related MRs on board issue detail sidebar ~"Plan", devopsplan, feature, ~"group::team planning" -
#12522 (closed) Service Desk - complete mail, when opening a new ticket ~"Plan", devopsplan, feature, ~"group::team planning" -
#12435 Add attribute to specify an issue template while creating an issue via API ~"Plan", api, devopsplan, feature, ~"group::team planning", issues -
#12285 (closed) Allow glob filtering of scoped labels ~"Plan", devopsplan, feature, ~"group::team planning", internal customer, labels -
#12243 (closed) Not possible to hide requester's e-mail when making Service Desk issues public ~"Category::Service Desk", ~"Plan", auto updated, devopsplan, feature, ~"group::team planning", issues -
#12194 (closed) Showing progress more accurately in burndown chart ~"Plan", burndown/up charts, devopsplan, feature, ~"group::team planning" -
#12125 (closed) More Accessible and Conventional Epics ~"Category::Agile Portfolio Management", ~"Plan", UX, UX research, devopsplan, epics, feature, ~"group::portfolio management" -
#11950 (closed) Allow users to create an issue from within an Epic ~"Plan", customer, feature -
#11948 (closed) Ability to associate issue with an Epic from the issue ~"Plan", customer, feature -
#11819 Separate progress bar / percentage for MRs in a milestone ~"Plan", UX, backend, devopsplan, feature, frontend, milestones
Hi @donaldcook,
Here is a list of frontend bugs without severity and priority for the team.
We would like to ask you to work with your team to triage the issues in this list. For each issue please:
- Close the issue if it is no longer relevant or a duplicate.
- Assign a Priority and a Severity Label.
- Assign either a versioned milestone or to the %Backlog milestone.
The definition of these labels are defined at:
- Priority Labels (~P1 / ~P2 / ~P3 / ~P4)
- Severity Labels (~S1 / ~S2 / ~S3 / ~S4)
For the issues triaged please check off the box in front of the given issue.
Please work with your team to complete the list this week.
-
#12775 (closed) Hide issue boards switcher if multiple issue boards are not available ~"Category::Issue Boards", ~"Plan", ~"bug", devopsplan, frontend, ~"group::team planning", reproduced on GitLab.com
This is a group level triage package that aims to collate the latest bug reports (for frontend and otherwise) and feature proposals. For more information please refer to the handbook: