2019-09-16 - Triage report for "group::release management"
Hi, @ogolowinski @darbyfrey @jhampton
This is a group or stage level triage package that aims to summarize the feature proposals and bugs which have not been scheduled or triaged. For more information please refer to the handbook:
Scheduling the workload is a collaborative effort by the Product Managers and Engineering Managers for that group. Please work together to provide a best estimate on priority and milestone assignments. For each issue please:
- Determine if the issue should be closed if it is no longer relevant or a duplicate.
- If it is still relevant please assign either a best estimate versioned milestone, the %Backlog or the %Awaiting further demand milestone.
- Specifically for ~bug, if there is no priority or clarity on a versioned milestone, please add a Priority label. Priority labels have an estimate SLO attached to them and help team members and the wider community understand roughly when it will be considered to be scheduled.
- Once a milestone has been assigned please check off the box for that issue.
- Please work with your team to complete the list by the due date set.
Unscheduled feature (non-customer)
-
#14955 (closed) Pagination missing on Releases page ~"devops::release", feature, ~"group::release management"
Bug Section
For the following bugs. Please either close or assign either a versioned milestone, the %Backlog or the %Awaiting further demand milestone and ensure that a priority label is set.
Heatmap for all bugs
Bugs for their priority and severity label are counted here. Every bug should have severity and priority labels applied. Please take a look at the bugs which fall into the columns indicating that the priority or severity labels are currently missing.
| ~S1 | ~S2 | ~S3 | ~S4 | ~"No severity" | |
|---|---|---|---|---|---|
| ~P1 | 0 | 0 | 0 | 0 | 1 |
| ~P2 | 0 | 8 | 1 | 0 | 0 |
| ~P3 | 0 | 1 | 42 | 2 | 0 |
| ~P4 | 0 | 0 | 13 | 19 | 0 |
| ~"No priority" | 0 | 1 | 0 | 2 | 0 |
Unscheduled ~bug (non-customer)
-
#31531 (closed) Files links attached to tags are broken on releases view in private projects ~"S2", ~"bug", ~"devops::release", ~"group::release management" -
#31323 (closed) There is no information in the Merge Request description about environments extracted from the tag ~"P4", ~"S4", ~"bug", devopscreate, environments, ~"group::release management", merge requests -
#31231 (closed) After upgrading to 12.2 Pages shows 404 when access control enabled Category:Pages, ~"S4", ~"bug", ~"devops::release", ~"group::release management" -
#30977 (closed) Some browsers are getting server responses from GitLab proper instead of Pages Category:Pages, ~"P4", ~"S4", ~"bug", ~"devops::release", ~"group::release management" -
#30470 Order of asset links in a release is not defined Category:Continuous Delivery, ~"P4", ~"Release [DEPRECATED]", ~"S4", ~"bug", ~"devops::release", ~"group::release management" -
#30395 (closed) Pages hosted on gitlab.io have a broken TLS cert for some users Category:Pages, ~"P2", ~"Release [DEPRECATED]", ~"S2", ~"bug", ~"devops::release", ~"group::release management" -
#30222 (closed) Automatic Certificate Management with Let's Encrypt applies *.gitlab.io certificate during setup Category:Pages, ~"P3", ~"Release [DEPRECATED]", ~"S3", ~"bug", ~"devops::release", ~"group::release management", ~"release::validation::backlog" -
#29765 (closed) On releases page commit hashes are not linked ~"S4", ~"bug", ~"devops::release", ~"group::release management", markdown, repository -
#29708 (closed) Project settings pages access control label misleading, fully disables pages Category:Pages, ~"P4", ~"Release [DEPRECATED]", ~"S4", UX, ~"bug", ~"devops::release", ~"group::release management", ~"release::validation::backlog" -
#28943 (closed) pages:deploy not getting triggered when using hidden pages job Category:Pages, ~"P3", ~"Release [DEPRECATED]", ~"S3", ~"bug", ~"devops::release", ~"group::release management" -
#28635 (closed) Gitlab.com Pages: Verification does not recongize txt entires for CNAME entries Category:Pages, ~"P2", ~"S2", ~"bug", ~"devops::release", ~"group::release management", ~"missed-SLO" -
#28393 (closed) pages:deploy failing and sending emails even when pages has "allow_failure: true" Category:Pages, ~"P3", ~"Release [DEPRECATED]", ~"S3", ~"bug", ~"devops::release", ~"group::release management" -
#27945 (closed) No warning for wrong parameter in release API Category:Release Orchestration, ~"P3", ~"Release [DEPRECATED]", ~"S3", api, ~"bug", ~"devops::release", ~"group::release management", ~"release::validation::backlog" -
#27880 (closed) Clearing Release Notes Deletes Release Category:Release Orchestration, ~"P2", ~"Release [DEPRECATED]", ~"S2", backend, ~"bug", ~"devops::release", ~"group::release management", ~"missed-SLO", ~"release::validation::backlog" -
#27868 (closed) Detail view on stopped environment shows stop button Category:Release Orchestration, ~"P4", ~"Release [DEPRECATED]", ~"S4", UI polish, ~"bug", ~"devops::release", ~"group::release management"
Heatmap for ~missed-SLO bugs
| ~S1 | ~S2 | ~S3 | ~S4 | |
|---|---|---|---|---|
| ~P1 | 0 | 0 | 0 | 0 |
| ~P2 | 0 | 6 | 1 | 0 |
| ~P3 | 0 | 0 | 0 | 0 |
| ~P4 | 0 | 0 | 0 | 0 |
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: