<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=280771) </details> <!--IssueSummary end--> ### Problem to solve <!-- What problem do we solve? Try to define the who/what/why of the opportunity as a user story. For example, "As a (who), I want (what), so I can (why/value)." --> Today, when a user clicks on a job to access the logs in order to troubleshoot after a failed status or just to check the progress of the job, they are presented with the log details as a bulk. To be able to make sense of the information they are viewing at, users have to scour/browse through the entire log and manually spot the section that concerns them. ### Intended users * [Delaney (Development Team Lead)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#delaney-development-team-lead) * [Sasha (Software Developer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sasha-software-developer) * [Devon (DevOps Engineer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#devon-devops-engineer) ### User experience goal Organize the content in the logs and reduce the effort to spot a discrepancy or error. ### Proposal Segregate the information in the logs into collapsible sections with identifiable names and associated status so users know exactly where to look at to counter a specific problem. <!-- How are we going to solve the problem? Try to include the user journey! https://about.gitlab.com/handbook/journeys/#user-journey --> - Today we already provide users the ability to define pre-collapsed sections. Instead of making this a configurable, we should collapse the section by default to make it more readable - When collapsed, the sections are flattened. Add required hierarchy through nesting sections when necessary ### Further details <!-- Include use cases, benefits, goals, or any other details that will help us understand the problem better. --> ### Links / references <!-- Label reminders - you should have one of each of the following labels. Read the descriptions on https://gitlab.com/gitlab-org/gitlab/-/labels to find the correct ones -->