Audit: Identify all build related empty states
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Objective
We mostly come across projects that have considerable amount of resources hosted into them already and hence don't get a complete picture of what new users see. Hence, we lack visibility into what the various empty states in CI/CD look like, and there have been some changes that were not ran through the design DRIs of the stage groups.
Example: this shows when no pipeline is added to a project and the concerned team has no knowledge of this addition.
This highlight the need to pro-actively track these empty states to understand which frameworks we can employ next to make them more helpful for our users while aligning the actions with our business direction.
Who will participate?
| DRI | Pages/Area | Stage-group |
|---|---|---|
| Sunjung | Pipeline editor, CI Catalog, Pipeline graph, tabs in the pipeline detail page | Pipeline Authoring |
| Gina | Runner(at all levels), Runner settings, Runner management area | Runner management |
| Veethika | Pipeline list view, Jobs list view, merge status widget(CI/CD related, pipeline tab in MRs, Job logs |
Pipeline Execution Pipeline Security |
| Activity | Goal | Issue |
|---|---|---|
| Audit | Understand where we're at with the current empty states and which components and pages lack an empty state |
|
| Map empty states | Align the empty states in CI/CD with documented JTBDs and create a logical map on how they'd relate and connect | #425860 |
| Create issues | Identify the changes we need to make to all empty states and discuss with leadership to develop a plan of action | &11532 |
FigJam Board
You may reference this old issue.