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/11437 Group labels with the same colon prefix together ~"Plan", feature, labels -
https://gitlab.com/gitlab-org/gitlab-ee/issues/11402 Instance Level Epics ~"Plan", feature -
https://gitlab.com/gitlab-org/gitlab-ee/issues/11391 After moving Service Desk issue, email comes in at original (closed) issue ~"Category::Service Desk", ~"P4", ~"Plan", ~"S4", ~"bug", customer, ~"devops:plan", feature -
https://gitlab.com/gitlab-org/gitlab-ee/issues/11327 Using "UPCOMING" filter for Milestones in Board Configuration also includes current/started Milestone ~"Plan", ~"devops:plan", feature, milestones -
https://gitlab.com/gitlab-org/gitlab-ee/issues/11241 Epic API missing web_url
field GitLab Ultimate, ~"Plan", api, ~"devops:plan", epics, feature -
https://gitlab.com/gitlab-org/gitlab-ee/issues/11240 Epic API missing subscribed
field GitLab Ultimate, ~"Plan", api, ~"devops:plan", epics, feature -
https://gitlab.com/gitlab-org/gitlab-ee/issues/11239 Epic API missing closed_at
field GitLab Ultimate, ~"Plan", api, ~"devops:plan", epics, feature -
https://gitlab.com/gitlab-org/gitlab-ee/issues/11228 Closed issues still show due dates in red ~"Plan", ~"devops:plan", feature, usability -
https://gitlab.com/gitlab-org/gitlab-ee/issues/11197 Gitlab intgrate to Elasticsearch 7.0 release date? ~"Plan", ~"devops:plan", ~"elasticsearch", feature -
https://gitlab.com/gitlab-org/gitlab-ee/issues/11167 Import JIRA Epics as project Milestones GitLab Premium, ~"Plan", customer+, ~"devops:plan", feature -
https://gitlab.com/gitlab-org/gitlab-ee/issues/4335 Service Desk: Separate Issue Comments from Email Replies ~"Category::Service Desk", ~"Plan", auto updated, awaiting feedback, emails, feature -
https://gitlab.com/gitlab-org/gitlab-ee/issues/4323 Support epic subscriptions and email notifications ~"Category::Agile Portfolio Management", GitLab Ultimate, ~"Plan", UX, auto updated, awaiting feedback, epics, feature -
https://gitlab.com/gitlab-org/gitlab-ee/issues/4169 enhancement for "approver" role of merge requests ~"Create", ~"P3", ~"Plan", ~"S3", approvals, awaiting feedback, customer, feature -
https://gitlab.com/gitlab-org/gitlab-ee/issues/4103 Group discussion board ~"Plan", ~"devops:plan", feature -
https://gitlab.com/gitlab-org/gitlab-ee/issues/4007 Allowing LDAP groups to be configure as Approvers for merge requests. ~"Create", ~"Manage", ~"Plan", approvals, auto updated, awaiting feedback, feature, ldap
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/11529 Not possible to set weight of board scope to None or 0 ~"Accepting merge requests", ~"Category::Issue Boards", ~"Plan", ~"S2", blocked, ~"bug", ~"devops:plan", frontend, reproduced on GitLab.com
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/11517 JIRA Development Panel Integration: list repo is empty ~"Jira", ~"Plan", ~"bug"
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: