Verify group issues requiring attention
Hi @brendan,
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/11217 Display full, variable interpolated job details in a descriptive format ~"Verify", ~"devops:verify", feature -
https://gitlab.com/gitlab-org/gitlab-ee/issues/3632 Version control for project and group variables ~"Verify", ~"devops", ~"devops:verify", feature -
https://gitlab.com/gitlab-org/gitlab-ee/issues/3540 Allow customers to specify additional URL's to test ~"Category::Performance Testing", ~"Monitor", ~"Verify", ~"devops:verify", direction, feature -
https://gitlab.com/gitlab-org/gitlab-ee/issues/3450 Rerun pipeline/job on specific runner and/or tag ~"Verify", ~"devops:verify", feature, pipeline -
https://gitlab.com/gitlab-org/gitlab-ee/issues/3410 Gatekeeper ~"Verify", deploy, ~"devops", ~"devops:verify", feature -
https://gitlab.com/gitlab-org/gitlab-ee/issues/3294 GitLab CI should be able to use specific Geo secondary to clone from ~"Geo", ~"Geo Replication/Sync", ~"P3", ~"S3", ~"Verify", customer, ~"devops:verify", feature -
https://gitlab.com/gitlab-org/gitlab-ee/issues/3246 Multi-project pipeline dashboard UX, ~"Verify", ~"devops:verify", feature, test -
https://gitlab.com/gitlab-org/gitlab-ee/issues/3234 Implement custom job scheduling through a user defined script to increase utilisation of CI runner resource usage ~"Verify", ~"devops:verify", feature -
https://gitlab.com/gitlab-org/gitlab-ee/issues/3111 Better highlighting of repeat job failures / Ability to see recent failures for a branch UX, ~"Verify", ~"devops:verify", feature -
https://gitlab.com/gitlab-org/gitlab-ee/issues/2748 Cross-project connections outside .gitlab-ci.yml~"Verify", ~"devops:verify", feature, meta -
https://gitlab.com/gitlab-org/gitlab-ee/issues/2620 Merging when build succeeds merges in subsequent unbuilt changes to source branch ~"Create", ~"Verify", ~"devops:verify", ~"external services", feature, merge requests -
https://gitlab.com/gitlab-org/gitlab-ee/issues/2511 A CI configuration button in the Pipeline tab. UX, ~"Verify", awaiting feedback, ~"devops:verify", feature, pipeline -
https://gitlab.com/gitlab-org/gitlab-ee/issues/2505 Pipeline timing graphs ~"Category::Continuous Integration", GitLab Starter, UX, ~"Verify", customer+, ~"devops:verify", direction, feature -
https://gitlab.com/gitlab-org/gitlab-ee/issues/2455 only/except behaviour when matching both ~"Verify", ~"devops:verify", feature, pipeline -
https://gitlab.com/gitlab-org/gitlab-ee/issues/2453 Mirrored dependencies to increase reproducibility, security, and speed ~"Verify", ~"devops:verify", feature
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.
-
https://gitlab.com/gitlab-org/gitlab-ee/issues/11100 Ensure all ENV variables are propagated to codequality job ~"Category::Code Quality", ~"Verify", ~"bug", ~"devops:verify" -
https://gitlab.com/gitlab-org/gitlab-ee/issues/11087 Downstream triggers passes all variables ~"Verify", ~"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: