Discuss current problems with issue boards design
As pointed out by @cperessini in https://gitlab.com/gitlab-org/gitlab-ce/issues/33023#note_84293316, boards are starting to become a bit too bloated from an interaction POV. There are board configs, board filters, assignee lists, label lists, milestone lists, and next burndown charts in boards and maybe even multiple board views
Identified “problems” and issues to revisit
-
Navigating and managing multiple issue boards:
- Continuously growing list of boards — as people create them per milestone
- Should it be possible to 'close' or 'archive' a board, rather than delete it?
- Better discovery - there is no link from an issue to the boards it's on, for instance.
- Backlog column is confusing
- Default board for everyone
- Option to pin backlog on the left
- How to plan milestones
- Permanently scoping boards across the application
- Multiple views
- Swimlanes
- Board types
- Value Stream Analytics
- Saved configuration for issue board
- Multiple labels per board list
- Save filter with issue board
- Replace plan issues with issue board
- Issue board as a workflow tool
- Surface the board's scope
Completed UX research
Edited by Pedro Moreira da Silva