Plan group issues requiring attention
Hi @victorwu,
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.
-
https://gitlab.com/gitlab-org/gitlab-ee/issues/10260 Single list for epics and issues Persona: Product Manager, ~"Plan", ~"devops:plan", epics, feature, issues -
https://gitlab.com/gitlab-org/gitlab-ee/issues/9886 Make promoted epics a child of the original issue's epic ~"Plan", backend, feature -
https://gitlab.com/gitlab-org/gitlab-ee/issues/9863 Planning Poker (for distributed Teams) ~"Plan", ~"devops:plan", feature, issue weight -
https://gitlab.com/gitlab-org/gitlab-ee/issues/9676 Epic autocomplete does not find epics from ancestor groups ~"Plan", ~"devops:plan", epics, feature -
https://gitlab.com/gitlab-org/gitlab-ee/issues/9660 Assign epics inside an issue ~"Plan", ~"devops:plan", epics, feature, issues -
https://gitlab.com/gitlab-org/gitlab-ee/issues/9468 Embed Salesforce details in issue ~"Plan", feature -
https://gitlab.com/gitlab-org/gitlab-ee/issues/9472 Epic to Issue relationship enhancements ~"Plan", ~"devops:plan", epics, feature, issues -
https://gitlab.com/gitlab-org/gitlab-ee/issues/9285 Insert a link to the issue in emails from service desk ~"Plan", ~"Service Desk", emails, feature -
https://gitlab.com/gitlab-org/gitlab-ee/issues/9476 Epic detail should display time-tracking information ~"Plan", epics, feature -
https://gitlab.com/gitlab-org/gitlab-ee/issues/9110 Add the ability to sort on the various columns from the UI based upon specific dates or at least asc/desc order ~"Issue Boards", ~"Plan", awaiting feedback, feature -
https://gitlab.com/gitlab-org/gitlab-ee/issues/8686 Search for keywords in the comments of epics ~"Agile Portfolio Management", GitLab Ultimate, ~"Plan", customer, epics, feature -
https://gitlab.com/gitlab-org/gitlab-ee/issues/8595 Separate issue board actions ~"Issue Boards", ~"Plan", UX, ~"devops:plan", feature -
https://gitlab.com/gitlab-org/gitlab-ee/issues/8533 Logical operators in board scope GitLab Premium, ~"Issue Boards", ~"Plan", feature -
https://gitlab.com/gitlab-org/gitlab-ee/issues/8516 Group issues by milestone in an Epic ~"Plan", ~"devops:plan", epics, feature -
https://gitlab.com/gitlab-org/gitlab-ee/issues/8423 Add weight as possible board list for estimation meetings ~"Issue Boards", ~"Plan", ~"devops:plan", feature, issue weight
Hi @andr3,
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.
-
https://gitlab.com/gitlab-org/gitlab-ee/issues/10261 Dropdowns in edit board modal are misaligned ~"In review", ~"Issue Boards", ~"Plan", ~"S4", ~"bug", ~"devops:plan", frontend, regression, regression:11.8, reproduced on GitLab.com -
https://gitlab.com/gitlab-org/gitlab-ee/issues/10217 Board scope weight dropdown doesn't render properly ~"Plan", ~"bug", frontend -
https://gitlab.com/gitlab-org/gitlab-ee/issues/9653 When you reorder issues & epics in an epic, the outer box jumps in size a bit ~"Plan", ~"bug", epics, frontend -
https://gitlab.com/gitlab-org/gitlab-ee/issues/9522 Changing weight of newly created issue fails on issue board sidebar ~"Accepting merge requests", ~"Issue Boards", ~"P3", ~"Plan", ~"bug", ~"devops:plan", frontend, issue weight, reproduced on GitLab.com -
https://gitlab.com/gitlab-org/gitlab-ee/issues/8403 Broken empty state image on issue analytics page ~"Accepting merge requests", ~"Plan", ~"bug", frontend, issues, regression, regression:11.5 -
https://gitlab.com/gitlab-org/gitlab-ee/issues/3305 Adding related issue does not complete todo ~"Plan", auto updated, awaiting feedback, ~"bug", ~"devops:plan", frontend
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.
-
https://gitlab.com/gitlab-org/gitlab-ee/issues/10270 Milestones should not be set on epics (issue promotion) ~"Plan", backend, ~"bug", epics -
https://gitlab.com/gitlab-org/gitlab-ee/issues/10234 Group level issue board scoped to running milestone show to many closed issues ~"Accepting merge requests", ~"Issue Boards", ~"P3", ~"Plan", awaiting feedback, ~"bug", ~"devops:plan"
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: