Issue details page redesign
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 9
- Forks
- 31
- Avg merge
- 3d 19h
- Merged PRs (30d)
- 16
Description
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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the attached mock and compare it with the current Issue Details page. No files, tests, or entry points are named; gather feedback on the proposed hierarchy and record an agreed design direction before implementation begins.
Written by the indexing model from the issue text.
Assessment
- Domain
- design, frontend, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100