Discuss the use of pipeline status icons
Problem
What we have been referring to pipeline icons
or pipeline status icons
for long has been found useful in different contexts in the while. (example : services in environments).
We often discuss extending the use of these icons beyond pipelines. Here's an opportunity to get on the same page through discussions so we can establish some guidelines around this.
Findings so far
- Users get confused when they're not quickly able to locate the status of pipelines because everything else looks like them
- Expect the badges to be clickable, as they are for pipelines list page
- There are scenarios when more than one resources are being represented on one page and their status requires to be shown as well.
- There's usually no complains when a singular resource(non-pipeline) is shown on a page and its using the pipeline status icon.
What we have today:
- Pipeline status icons
- Merge status icons
- Severity icons
What's lacking
- Guidelines around the applications
- Status icons with variants designed different attention level that can fit a range of context(online/offline, success/failure, heathy/unhealthy, etc.)
Links from competitors
Benchmark research insight
Users saw conflicting status reports on the same page(merge request page).
FigJam board(add examples here)
Edited by Veethika Mishra