Frontend: Improve artifacts bulk list UX
Summary
Follow up from !121900 (comment 1415599857).
Feedback from UX:
It seems from the design on the original issue that when a job only has 1 artifact, we just list it out rather than having it within a collapsed area (and essentially duplicating some of the info/actions).
We got some UX feedback regarding this new feature, let's discuss how we can improve the users experience.
Per comments below:
In this issue we should only focus on adding the indentation to the child items. Any other improvements wouldn't have a larger impact so we should approach those later when we have capacity to relook into the artifacts list view experience.
Proposal
- Add the indentation to the child items
Out of Scope
a) single-artifact jobs should be expanded by default: We should show the job "folder" row as expanded, with the artifact row below it, if the job has only one artifact. This way, you don't have to click to expand the row in order to delete the single artifact.
b) single artifacts should be shown without their job "folder"s: We should not show the job "folder" row, and only show the artifact row, if the job has only one artifact. This way, a single artifact isn't grouped for no reason and redundant buttons are not shown.
Additional details
Some relevant technical details, if applicable, such as:
- Does this need a feature flag?
- Does there need to be an associated instrumentation issue created related to this work?
- Is there an example response showing the data structure that should be returned (new endpoints only)?
- What permissions should be used?
- Is this EE or CE?
-
EE -
CE
-
- Additional comments:
Implementation Table
Group | Issue Link |
---|---|
frontend |
|
Links/References
cc @nickbrandt