Issues to apply severity and priority for Release
Hi @darbyfrey,
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 and add a severity label (~S1 / ~S2 / ~S3 / ~S4) and a priority label (~P1 / ~P2 / ~P3 / ~P4) to the issues in this list.
The definition of these labels are defined at:
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.
-
Release notes button on tags page is confusing ~"Accepting merge requests", ~"Release", UX, ~"bug", ~"devops:release", ~"release orchestration" -
Allow specification of release date for Releases ~"Accepting merge requests", ~"Release", UX, ~"bug", ~"devops:release", ~"release orchestration" -
Use of tags between releases and tags pages is confusing ~"Accepting merge requests", ~"Release", UX, ~"bug", ~"devops:release", ~"release orchestration" -
Tags RSS feed 500 error ~"Accepting merge requests", ~"Release", ~"bug", ~"devops:release", repository -
GitLab-CI deploys to GitLab Pages for subgroup projects without aborting the operation ~"Accepting merge requests", ~"Manage", ~"Release", ~"bug", ~"devops:release", ~"pages", subgroups -
Environment not being created ~"Accepting merge requests", ~"Release", ~"bug", ~"devops:release" -
Delete/move docker registry repositories when the gitlab projects are moved/deleted ~"Accepting merge requests", ~"Release", ~"bug", container registry expert, customer, ~"devops:release" -
Project Variables API should allow filtering/creating/updating/deleting by environment_scope ~"Accepting merge requests", ~"Release", api, awaiting feedback, ~"bug", ~"ci variables", ~"devops:release" -
Environments not updating after manual build ~"Accepting merge requests", ~"Release", ~"bug", deploy, ~"devops:release"
/cc @nolith
Edited by Darby Frey