2020-12-14 - Triage report for "group::pipeline authoring"
Hi, @dhershkovitch @cheryl.li @samdbeckham @nadia_sotnikova
This is a group or stage level triage report 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)
-
gitlab-org/gitlab#292930 (closed) Breakdown
pipeline_editor_app
into smaller components ~"Category:Pipeline Authoring", devopsverify, ~"feature", ~"feature::maintenance", frontend, grouppipeline authoring, sectionops - gitlab-org/gitlab#292002 (closed) Add dropdown affordance to mini pipeline graph ~"Actionable Insight", ~"Category:Pipeline Authoring", UX, UX FY21-Q4, ~"bug", devopsverify, ~"feature", featureenhancement, grouppipeline authoring, merge request widget, merge requests, pipeline, pipeline graphs, sectionops, severity4
-
gitlab-org/gitlab#291726 (closed) Support
needs:
indicating specific combination(s) from aparallel:matrix:
job ~"Category:Pipeline Authoring", devopsverify, ~"feature", grouppipeline authoring, ~"pipeline dag", sectionops - gitlab-org/gitlab#290695 (closed) Create a visual pipeline builder ~"Category:Pipeline Authoring", SUS Survey, auto updated, devopsverify, ~"feature", grouppipeline authoring, pipeline, sectionops
- gitlab-org/gitlab#285853 [matrix job] allow customization of resulting job name ~"Category:Pipeline Authoring", devopsverify, ~"feature", featureenhancement, grouppipeline authoring, sectionops
- gitlab-org/gitlab#281351 (closed) Instrumenting the Big Pipeline Graph ~"Category:Pipeline Authoring", auto updated, ~"candidate::13.8", devopsverify, ~"feature", grouppipeline authoring, sectionops
- gitlab-org/gitlab#276480 (closed) Highlight the Pipeline Editor in the navigation with hotspot highlight ~"1st time experience", ~"Accepting merge requests", ~"Actionable Insight", ~"Category:Pipeline Authoring", UX, candidate13.9, devopsverify, ~"feature", grouppipeline authoring, sectionops, workflowplanning breakdown
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.
- Engineering Managers: Please add a severity label for those issues without one
- Product Designers: Please add a severity label to UX ~bug issues without one
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.
severity1 | severity2 | severity3 | severity4 | No severity | |
---|---|---|---|---|---|
priority1 | 2 | 0 | 0 | 0 | 0 |
priority2 | 0 | 26 | 8 | 0 | 1 |
priority3 | 0 | 2 | 110 | 6 | 0 |
priority4 | 0 | 0 | 4 | 31 | 0 |
No priority | 0 | 0 | 2 | 2 | 2 |
frontend ~bug (non-customer)
Unscheduled- gitlab-org/gitlab#291092 (closed) UI loses pipeline status icon when child pipeline was started execution ~"Category:Pipeline Authoring", ~"bug", ~"candidate::13.8", devopsverify, frontend, grouppipeline authoring, pipeline graphs, reproduced on GitLab.com, sectionops, workflowplanning breakdown
Unscheduled ~bug (non-customer)
-
gitlab-org/gitlab#292658 (closed) Fix
include
keyword inCiLint
graphql query ~"Category:Pipeline Authoring", ~"VerifyP1", backend, ~"bug", ~"candidate::13.8", devopsverify, grouppipeline authoring, sectionops, workflowplanning breakdown - gitlab-org/gitlab#292002 (closed) Add dropdown affordance to mini pipeline graph ~"Actionable Insight", ~"Category:Pipeline Authoring", UX, UX FY21-Q4, ~"bug", devopsverify, ~"feature", featureenhancement, grouppipeline authoring, merge request widget, merge requests, pipeline, pipeline graphs, sectionops, severity4
- gitlab-org/gitlab#291996 (closed) CI Lint cannot be accessed on new projects ~"Category:Pipeline Authoring", ~"bug", devopsverify, grouppipeline authoring, ~"pipeline authoring", sectionops, severity3
-
gitlab-org/gitlab#291743 (closed) Pipeline using
only:changes
feature reports incorrect error and does not trigger required upstream dependencies. CI rules, ~"Category:Pipeline Authoring", ~"bug", devopsverify, grouppipeline authoring, sectionops, severity3 - gitlab-org/gitlab#291050 Gitlab rejects the <COLON><SPACE> sequence in string in CI jobs ~"Category:Pipeline Authoring", ~"bug", devopsverify, grouppipeline authoring, sectionops, severity4
- gitlab-org/gitlab#281878 (closed) delayed and manual jobs with DAG are not skipped even they need a failed job ~"Category:Pipeline Authoring", ~"bug", ~"candidate::13.8", devopsverify, grouppipeline authoring, priority1, sectionops, severity1, workflowready for development
Heatmap for ~missed-SLO bugs
severity1 | severity2 | severity3 | severity4 | No severity | |
---|---|---|---|---|---|
priority1 | 0 | 0 | 0 | 0 | 0 |
priority2 | 0 | 20 | 0 | 0 | 0 |
priority3 | 0 | 2 | 2 | 0 | 0 |
priority4 | 0 | 0 | 0 | 0 | 0 |
No priority | 0 | 0 | 0 | 0 | 1 |
vintage bugs
Heatmap forseverity1 | severity2 | severity3 | severity4 | No severity | |
---|---|---|---|---|---|
priority1 | 0 | 0 | 0 | 0 | 0 |
priority2 | 0 | 0 | 0 | 0 | 0 |
priority3 | 0 | 0 | 6 | 0 | 0 |
priority4 | 0 | 0 | 1 | 0 | 0 |
No priority | 0 | 0 | 0 | 0 | 0 |
This is a group level triage report that aims to collate the latest bug reports (for frontend and otherwise) and feature proposals. For more information please refer to the handbook:
If assignees or people mentioned in this individual triage report need to be amended, please edit group-definition.yml.