Issue ideation (Cross-sprint) - 馃搫 Issue refactor
Purpose of this issue
This issue can house discussion or resources as we ideate on Issue within the Issue Refactoring project.
Scope
What is the ideal Issue view?
- What is the general structure/IA?
- How do we optimize the user's general flow as they interact with the view from a usability perspective?
- How might we address impactful UX debt or user frustrations pertaining to the view?
- Which objects are included to achieve consistency across issuables?
- What happens when the view is transformed?
- Promoted, moved, closed, cloned/duplicated
Objects included in each view
- What are the highest priority objects?
- What objects must be included by default?
Relationships of objects
- How might we ideally display the hierarchy or relationship of work items within a view?
- Issue <> Issue
- Issue <> MR
- etc
Edited by Alexis Ginsberg