Package group issues requiring attention

Hi @trizzi and @jlenny,

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.

  • #5815 (closed) Artifact repository specific subdomain ~"Package", ~"Package Registry", devopspackage, feature

Hi @dcroft,

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.

  • #11867 (closed) NPM Registry Endpoint Response Lacks Package Dependency Metadata; Breaks NPM GitLab Premium, ~"Package", ~"Package Registry", ~"bug", devopspackage, reproduced on GitLab.com


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
Assignee Loading
Time tracking Loading