Verify group issues requiring attention

Hi @brendan 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.

  • #11828 (closed) Trigger downstream pipeline dependencies ~"Verify", backend, ~"backstage", customer, depth, devopsverify, direction, feature, internal customer, pipeline
  • #11827 (closed) Track dependencies for automatically triggering pipelines ~"Verify", backend, ~"backstage", customer, depth, devopsverify, direction, feature, internal customer, pipeline
  • #11549 (closed) Use CI/CD UI variables to define parallelism ~"Accepting merge requests", ~"Category::Continuous Integration", ~"Verify", ~"ci variables", devopsverify, feature
  • #2354 Pipeline analyses to find transient failure ~"Category::Continuous Integration", GitLab Ultimate, ~"Manage", ~"Verify", customer, devopsverify, direction, feature
  • #2098 (closed) CI Executive Dashboards ~"Verify", devopsverify, feature
  • #2025 Dashboard view of consolidated chart and stats for build health ~"Verify", devopsverify, feature, pipeline
  • #1771 Download public projects build artifacts without authentication token ~"Verify", ~"artifacts", devopsverify, feature, permissions
  • #1683 (closed) Controllable permissions for CI tokens GitLab Premium, ~"Verify", direction, feature, pipeline
  • #1682 More control over manual action permissions GitLab Premium, ~"Verify", direction, feature
  • #1636 (closed) Suggest to setup and use CI if no CI is setup in a project ~"Create", ~"Manage", UX, ~"Verify", devopsverify, feature
  • #1533 Notification of CI status regardless of current navigation status ~"Verify", devopsverify, feature, frontend
  • #1518 Performance statistics for each line of a build ~"Verify", devopsverify, feature
  • #1516 (closed) Pipeline designer - visualized editing of pipelines ~"Verify", devopsverify, feature, frontend
  • #1515 Allow use of Jenkins as a GitLab runner ~"Verify", devopsverify, feature, ~"jenkins"
  • #1430 (confidential) ~"(confidential)"

Hi @erushton,

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.

  • #11882 (closed) Passing variables to downstream pipeline not behaving as described/intended ~"Category::Continuous Integration", ~"Verify", ~"bug", ~"ci variables", devopsverify, reproduced on GitLab.com
  • #11818 (closed) Code Quality MR widget blocks the whole MR detail web UI while loading ~"Category::Code Quality", ~"Verify", ~"bug", devopsverify
  • #11786 (closed) Merge Request Jenkins Race Condition ~"Verify", ~"bug", devopsverify, ~"external services", merge requests, pipeline
  • #11522 (closed) Codecimate had hardcoded image repositories ~"Verify", ~"bug"
  • #11100 (closed) Ensure all ENV variables are propagated to codequality job ~"Category::Code Quality", ~"Verify", ~"bug", devopsverify
  • #11087 (closed) Downstream triggers passes all variables ~"Verify", ~"bug"
  • #10352 (closed) ERROR: Registering runner... failed ~"Category::Continuous Integration", ~"Verify", awaiting feedback, ~"bug", devopsverify, support request


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 Jun 11, 2019 by Brendan O'Leary
Assignee Loading
Time tracking Loading