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.

  • #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 (closed) 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
  • #11327 Using "UPCOMING" filter for Milestones in Board Configuration also includes current/started Milestone ~"Plan", devopsplan, feature, milestones
  • #11241 (closed) Epic API missing web_url field GitLab Ultimate, ~"Plan", api, devopsplan, epics, feature
  • #11240 (closed) Epic API missing subscribed field GitLab Ultimate, ~"Plan", api, devopsplan, epics, feature
  • #11239 (closed) Epic API missing closed_at field GitLab Ultimate, ~"Plan", api, devopsplan, epics, feature
  • #11228 (moved) Closed issues still show due dates in red ~"Plan", devopsplan, feature, usability
  • #11197 (closed) Gitlab intgrate to Elasticsearch 7.0 release date? ~"Plan", devopsplan, ~"elasticsearch", feature
  • #11167 Import JIRA Epics as project Milestones GitLab Premium, ~"Plan", customer+, devopsplan, feature
  • #10556 (closed) Support adding an epics to a parent using quick action ~"Plan", epics, feature, quick actions
  • #4335 (closed) Service Desk: Separate Issue Comments from Email Replies ~"Category::Service Desk", ~"Plan", auto updated, awaiting feedback, emails, feature

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.

  • #11739 (closed) Scoped labels do not remove old label in board sidebar ~"Category::Issue Boards", ~"Plan", ~"bug", devopsplan, frontend, labels
  • #11737 (closed) Can't set weight on newly-created issue in board ~"Category::Issue Boards", ~"Plan", ~"bug", devopsplan, frontend, issue weight
  • #11736 (moved) Setting assignee is from boards is cancelled when you click outside the sidebar ~"Category::Issue Boards", ~"Plan", ~"bug", devopsplan, frontend
  • #11735 (closed) Upgrade plan in Issue board broken ~"Category::Issue Boards", ~"Plan", UI polish, ~"bug", devopsplan, frontend
  • #11748 (closed) Scoped labels are broken on the activity feed ~"Plan", UX, ~"bug", devopsplan, frontend, labels

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.

  • #11742 (closed) ui(board): order list not always saved ~"Category::Issue Boards", ~"Plan", ~"bug", devopsplan
  • #11741 (closed) ui(board): long lists lose issues ~"Category::Issue Boards", ~"Plan", ~"bug", devopsplan
  • #11733 (closed) Issue attachments cannot be downloaded from Service Desk email ~"Category::Service Desk", ~"Plan", ~"bug", devopsplan, ~"group::certify", reproduced on GitLab.com
  • #11703 (closed) Quick actions related to Epic hierarchy should only be available in PostgreSQL ~"Plan", backend, ~"bug", quick actions


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:

  • https://about.gitlab.com/handbook/engineering/quality/guidelines/triage-operations/#current-packages
Edited May 19, 2022 by Coung Ngo
Assignee Loading
Time tracking Loading