Navigating and managing multiple issue boards with multiple views
- For a given project or group, you can have many many boards.
- Right now it is a dropdown. That can become very difficult to manage with that increasingly long dropdown.
- Some teams may use boards as team boards, and others may use as personal boards. Is it confusing that these are not explicitly differentiated in the UI?
- Currently boards are often scoped permanently to milestones. This means that a user can create their own team board per milestone (in GitLabs case, for 9.2, 9.3, etc.). This is causing the list to grow and be cluttered with stale boards that persist after the milestone has ended. How can we solve the problem surrounding old boards being listed in the board switcher? Should we remove boards that have milestones attached that have already ended? What are the consequences to this?
Edited by Victor Wu