Plan group issues requiring attention
Heat map for bugs:
~S1 | ~S2 | ~S3 | ~S4 | ~"No severity" | |
---|---|---|---|---|---|
~P1 | 0 | 0 | 0 | 0 | 0 |
~P2 | 0 | 6 | 6 | 2 | 0 |
~P3 | 0 | 14 | 129 | 16 | 0 |
~P4 | 0 | 2 | 148 | 124 | 0 |
~"No priority" | 2 | 0 | 4 | 3 | 3 |
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.
-
#63835 (moved) Related Issues "Add" link button icon ~"Plan", UX, devopsplan, ~"feature", ~"group::team planning", issues -
#63765 (moved) Add more column to a CSV import in Issues. ~"Plan", ~"feature", ~"group::team planning", issues -
#63761 (moved) In issue board change the behavior of the closed issues list ~"Category::Issue Boards", ~"Plan", devopsplan, ~"feature", ~"group::team planning" -
#63718 (moved) Support disabled tasks in issues/MRs ~"Plan", ~"feature", task management -
#63616 (moved) Simplify creation of issues over email ~"Plan", ~"feature", ~"group::team planning", issues -
#63598 (moved) Feature request: Customisable security issue severities ~"Plan", devopsplan, ~"feature", ~"group::enterprise planning", labels -
#63495 (moved) Improved escalation process for overdue issues with certain labels ~"Plan", ~"Secure", devopsplan, ~"feature", internal customer -
#63370 (moved) Add ability to query epics from GraphQL API ~"Category::Agile Portfolio Management", ~"Plan", auto updated, devopsplan, epics, ~"feature", ~"group::enterprise planning" -
#63306 (moved) Make the style of list in Projects and Groups consistent ~"Plan", UX, devopsplan, ~"feature" -
#63183 (moved) Move the markdown editor to a third-party component, or refactor to roll our own ~"Plan", ~"backstage", devopsplan, ~"feature", frontend, ~"technical debt" -
#63179 (moved) Merge Request Pipeline JIRA ID validation as per JIRA ID valid or not and also ID should be in OPEN/INPROGRESS state to proceed Merge Request pipeline ~"Jira", ~"Plan", ~"Verify", devopsplan, ~"feature", ~"group::team planning", pipeline -
#63118 (moved) Manipulate issues when merging MR ~"Category::Issue Boards", ~"Plan", customer, devopsplan, ~"feature", ~"group::team planning", issues, merge requests -
#63108 (moved) Usability improvements for in-product roadmaps ~"Plan", devopsplan, ~"feature", internal customer, meta -
#63040 (moved) Make it possible to automatically insert the target issue title in addition to the ID when refering to issues or when duplicating an issue to another ~"Plan", devopsplan, ~"feature", ~"group::team planning" -
#62897 (moved) [Feature Request] Option to calculate Milestone progress ~"Category::Time Tracking", ~"Plan", devopsplan, ~"feature", ~"group::team planning", 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.
-
#63548 (moved) Inline math doesn't work for RTL languages ~"Plan", ~"S3", ~"bug", devopsplan, frontend, ~"group::team planning", markdown -
#63300 (moved) Export as CSV button does not scale on mobile ~"Plan", UX, ~"bug", devopsplan, frontend, ~"group::team planning"
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.
-
#63844 (closed) Epic roadmap timelines do not propagate up to the parent epic ~"Plan", ~"S3", ~"bug", devopsplan -
#63833 (closed) The JIRA integration does not work with a trailing slash in Web URL ver 12.0.0-ee ~"Jira", ~"Plan", ~"bug", devopsplan, ~"group::team planning" -
#63735 (closed) Chinese Label not work through a template ~"Manage", ~"Plan", ~"S4", ~"bug", devopsmanage, ~"group::measure", ~"internationalization", labels -
#63730 (closed) Showing 500 on page /admin/labels ~"Plan", ~"S1", ~"bug", devopsplan, ~"group::team planning", labels -
#63648 (moved) Clicking on a milestone's "xyz issue" link can lead to apparently wrong result of 0 issues found ~"Plan", ~"S3", ~"bug", devopsplan, ~"group::team planning", milestones -
#63608 (closed) Project homepage not sorted correctly since 12.0.0 ~"Category::Project Management", ~"Plan", ~"S1", ~"bug", devopsplan, regression, regression:12.0 -
#63606 (moved) Leading % character in rendered milestone status ~"Plan", ~"S4", UX, ~"bug", devopsplan, milestones -
#63521 (moved) UTF-8 encoded SVG with BOM are detected as text/plain ~"Plan", ~"S4", banzai, ~"bug", devopsplan, ~"group::team planning", markdown -
#63287 (moved) Header logo size ~"Plan", ~"bug", emails -
#63519 (moved) project searching pagination bug ~"Plan", ~"S3", awaiting feedback, ~"bug", devopsplan, ~"filter bar", ~"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: