Plan group issues requiring attention
Heat map for bugs:
~S1 | ~S2 | ~S3 | ~S4 | ~"No severity" | |
---|---|---|---|---|---|
~P1 | 0 | 0 | 0 | 0 | 0 |
~P2 | 0 | 4 | 2 | 0 | 0 |
~P3 | 0 | 0 | 39 | 10 | 0 |
~P4 | 0 | 0 | 12 | 13 | 0 |
~"No priority" | 0 | 1 | 0 | 1 | 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.
-
#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 -
#12125 (closed) More Accessible and Conventional Epics ~"Category::Agile Portfolio Management", ~"Plan", UX, UX research, devopsplan, epics, feature -
#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 -
#11794 Subscribe to Epic for updates ~"Plan", devopsplan, epics, feature -
#11715 (closed) Issue board: Filter by project/repository name ~"Category::Issue Boards", ~"Plan", devopsplan, feature -
#11592 Related issues across instances ~"Plan", UX, backend, devopsplan, feature, frontend, issues -
#11590 (closed) Support hundredths decimal place in issue weights ~"Plan", backend, customer, devopsplan, feature, frontend, issue weight, issues -
#11437 Group labels with the same colon prefix together ~"Plan", feature, labels -
#11402 Instance Level Epics ~"Plan", devopsplan, feature -
#11391 (closed) After moving Service Desk issue, email comes in at original (closed) issue ~"Category::Service Desk", ~"P4", ~"Plan", ~"S4", ~"bug", customer, devopsplan, feature
Hi @smcgivern,
Here is a list of 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.
-
#12469 (closed) Can't assign group milestone to project issue board ~"Category::Issue Boards", ~"Plan", ~"S2", ~"bug", devopsplan, milestones -
#12291 (closed) Fix error message when attempting to exceed the maximum epic depth of 5. ~"Plan", UX debt, ~"bug", devopsplan, epics, ~"group::team planning" -
#12192 (closed) New epic button is not correctly styled ~"Plan", ~"S4", UX, ~"bug", devopsplan, epics, ~"group::team planning"
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: