17.8 PA team Paper Cuts

Summary

• Improve viewing specific jobs in pipeline dropd... (#405347 - closed)
• Add subheadings for the failed jobs in PMG (#503189 - closed) -> Carried over to the next session

Definition of Done

Details

Roles involved

• Design
• Technical Writing
• Backend
• Frontend
• Test engineering

NOTE: When work is ready to be defined, please create appropriate sub-tasks.

added gitlab-org#14965 as parent epic

changed the description

added Category:Pipeline Composition devopsverify grouppipeline authoring sectionci labels

assigned to @sunjungp

changed milestone to %17.8

added UX label and removed Category:Pipeline Composition devopsverify sectionci labels

added devopsverify sectionci labels

marked the checklist item Design as completed

added UX Paper Cuts maintenanceusability typemaintenance usability labels

mentioned in issue gitlab-org/quality/triage-reports#20332 (closed)

mentioned in issue gitlab-org/quality/triage-reports#20448 (closed)

mentioned in issue gitlab-org/quality/triage-reports#20585 (closed)

mentioned in issue gitlab-org/ci-cd/pipeline-authoring#184 (closed)

changed the description

changed the description

changed the description

@bsandlin I added two items for 17.8 (not 17.7!). Do they look good in terms of scope? Let me know what you think!

@sunjungp This works! The divided list will be slightly more involved so I'd say we are probably at capacity for this paper cuts

Sounds good! I removed the draft from the issue. We could focus on one issue (divided list) maybe, up to you!

assigned to @bsandlin

added frontend label

marked the checklist item Frontend as completed

mentioned in issue gitlab-org/quality/triage-reports#20753 (closed)

mentioned in issue gitlab-org/quality/triage-reports#20833 (closed)

mentioned in issue gitlab-org/quality/triage-reports#20947 (closed)

mentioned in issue gitlab-org/quality/triage-reports#21137 (closed)

changed title from Draft: 17.8 PA team Paper Cuts to 17.8 PA team Paper Cuts

@bsandlin @nmezzopera I believe this issue is ready - but I would like to get your thoughts which workflow label suits the best after we reviewed the candidates in the list. Should this be workflowplanning breakdown or workflowready for development?

@sunjungp The candidates look good to me and I don't think we need to hash them out further. I've added workflowready for development

@bsandlin Thank you. Looking forward to the session!

added workflowready for development label

created branch 499676-17-8-pa-team-paper-cuts to address this issue

Debrief - we only covered the first issue, #405347 (closed) in our session today. The second issue will be covered another in the next session or independently.

Thanks for the collab @sunjungp! I will spin up an MR later today

/cc @nmezzopera @dhershkovitch

Thanks @bsandlin, great collaboration as always!

added design-weight1 label

changed the description

mentioned in merge request !175888 (merged)

added workflowin review label and removed workflowready for development label

Async status update

• Complete: 95%
• Confidence: 95%
• Notes:

MR in review - !175888 (merged)

Async status update

• Complete: 99%
• Confidence: 100%
• Notes: In verification

added workflowverification label and removed workflowin review label

Async status update

• Complete: 100%
• Confidence: 100%
• Notes: Complete

before	after

It's awesome Thank you so much, Briley!

Nice work @bsandlin

Thanks @seggenberger for collaboration on the design

Awesome work @bsandlin

@sunjungp @seggenberger @dhershkovitch Thanks team

added workflowcomplete label and removed workflowverification label

closed