Plan group issues requiring attention
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.
-
https://gitlab.com/gitlab-org/gitlab-ee/issues/11005 Jira Ticket Number Validation ~"Plan", feature -
https://gitlab.com/gitlab-org/gitlab-ee/issues/5441 Labels with associated milestone ~"Plan", UX, backend, feature, frontend, labels, milestones -
https://gitlab.com/gitlab-org/gitlab-ee/issues/5314 Better user experience when replacing the group with individuals of merge request approvers for specific MR ~"Create", ~"Plan", approvals, customer, feature -
https://gitlab.com/gitlab-org/gitlab-ee/issues/5169 Estimated completion date in roadmap epic bar ~"Category::Agile Portfolio Management", ~"Plan", ~"devops:plan", epics, feature, roadmaps -
https://gitlab.com/gitlab-org/gitlab-ee/issues/5168 Multiple group assignees in epic ~"Category::Agile Portfolio Management", ~"Plan", ~"devops:plan", epics, feature -
https://gitlab.com/gitlab-org/gitlab-ee/issues/7336 Create board scope for current milestones ~"Category::Issue Boards", ~"Plan", customer, feature, frontend -
https://gitlab.com/gitlab-org/gitlab-ee/issues/5053 Link GitLab merge request and commits to TFS work item GitLab Premium, ~"Plan", TFS, auto updated, awaiting feedback, ~"devops:plan", feature, potential proposal -
https://gitlab.com/gitlab-org/gitlab-ee/issues/4866 Encrypt data at rest CS Top 10 (2018CQ2), ~"Create", ~"Manage", ~"Plan", customer+, feature -
https://gitlab.com/gitlab-org/gitlab-ee/issues/4652 Service Desk should add CC'ed users to the issue ~"Category::Service Desk", ~"Plan", emails, feature -
https://gitlab.com/gitlab-org/gitlab-ee/issues/4520 Allow external related issues ~"Jira", ~"Plan", auto updated, awaiting feedback, ~"devops:plan", feature, issues -
https://gitlab.com/gitlab-org/gitlab-ee/issues/4460 Service Desk in groups ~"Category::Service Desk", ~"Plan", auto updated, awaiting feedback, feature, issues -
https://gitlab.com/gitlab-org/gitlab-ee/issues/4420 Set project masters as default merge request approver ~"Create", ~"Plan", approvals, customer, feature -
https://gitlab.com/gitlab-org/gitlab-ee/issues/4381 Linking to H-tags in descriptions of Issues/MR's doesn't change the visual of the url ~"Plan", UX, auto updated, awaiting feedback, feature -
https://gitlab.com/gitlab-org/gitlab-ee/issues/4362 Connect Issue comment thread (for service desk) to non gitlab user ~"Category::Service Desk", ~"Plan", auto updated, awaiting feedback, feature, issues -
https://gitlab.com/gitlab-org/gitlab-ee/issues/4342 Export CSV data malformed ~"Plan", customer, ~"devops:plan", feature, issues
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.
-
https://gitlab.com/gitlab-org/gitlab-ee/issues/11135 Scoped labels are overflowing container in labels page ~"Accepting merge requests", ~"P3", ~"Plan", ~"bug", frontend, regression, regression:11.10
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/11141 Scoped_label? method raises an exception on admin labels page ~"Plan", backend, ~"bug", regression, regression:11.10 -
https://gitlab.com/gitlab-org/gitlab-ee/issues/11021 Issue board has several updating bugs ~"Category::Issue Boards", ~"Plan", ~"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: