Browse feature should be easier to navigate when there are nested folders
Insight
The Browse feature needs to be easier to navigate through nested folders, while still showing the folder path. It would ideally lead them directly to the files to download/see.
Supporting evidence
if you have 10 folders nested and then artifact at the end, I would rather, you know, just click some buttons, expand all, or, you know, just, just go to the actual file rather than have to, you know, go from multiple pages and navigate through, through individual folders.
So let's say your artifact is created of four levels. And in one job you, you just change. And your file is right now, not on the fourth level, but on the third level currently, it's very hard to understand sort a difference, right? And especially if you have multiple artifacts, multiple folders, it's very hard to, to make a difference. So eventually you just have to download all the thing extract locally and then run some KDB and compare or anything like that to understand how, how they change.
If you don't have hard failure, let's say your job just tries to zip whatever is in the current directory. It won't fail. It will continue saying everything is green. And at the end, you know, the, the result of the job is totally wrong. And that's, again, brings us to the point where it would be nice to have some comparison how your artifact changes over the time. So you see massive change in the number of files or even in our archives. Right. It would be nice to show that within the archive, you have hundreds folders, 20 files or anything like that. Right. Because it gives you some understanding, even try to put side-by-sides how, how it has changed.
Action
Instead of making the user navigate through the file tree, where clicking into a folder brings you to a new page, we should show the whole file tree view so there is less navigation through pages. Also, browsing an artifact should bring them directly to that artifact file, with the tree opened, rather than starting at the beginning of the file tree (like the folder).
Resources
Tasks
-
Assign this issue to the appropriate Product Manager, Product Designer, or UX Researcher. -
Add the appropriate Group
(such as~"group::source code"
) label to the issue. This helps identify and track actionable insights at the group level. -
Link this issue back to the original research issue in the GitLab UX Research project and the Dovetail project. -
Adjust confidentiality of this issue if applicable