Context
The current Issue Details page is hard to scan. We could think about design improvements for it.
The attached mock is a proposed redesign of that page. Goal is to make the issue identity, status, and log excerpt obvious first, and push repeated metadata down.
What this mock changes
- Shorter header: status, error type, one-line summary, issue id
- At-a-glance strip: affected builds/tests, first/last seen
- Log excerpt moved up as the main content
- Empty fields hidden; raw/misc data collapsed
- Occurrences grouped so constant columns (tree, config, arch, compiler) sit in a group header instead of every row
Questions
- Does this hierarchy match how you actually use the page?
- Anything missing that you rely on today?
- Anything still redundant or too noisy?
Please comment on the screenshot. This is design-only — no implementation yet.
Visual reference
Context
The current Issue Details page is hard to scan. We could think about design improvements for it.
The attached mock is a proposed redesign of that page. Goal is to make the issue identity, status, and log excerpt obvious first, and push repeated metadata down.
What this mock changes
Questions
Please comment on the screenshot. This is design-only — no implementation yet.
Visual reference