Skip to content

GitLab Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
GitLab FOSS
GitLab FOSS
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 1
    • Merge Requests 1
  • Requirements
    • Requirements
    • List
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • GitLab.org
  • GitLab FOSSGitLab FOSS
  • Issues
  • #48847

Closed
Open
Opened Jul 04, 2018 by Pedro Moreira da Silva@pedroms🚧Developer

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 💥 Some issues are coming up (e.g. default board) that can be a result of this bloat and the problems may only compound unless we address this.

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

  • Quantitative analysis of boards on GitLab.com
  • Issue boards user interviews
  • Issues Workflow User Interviews
  • Exploratory interviews regarding project management / issues
  • Project & Group Level Tree Testing (Contextual Navigation)
  • Issue Display & Sort Order Survey
Edited Sep 05, 2018 by Pedro Moreira da Silva
Assignee
Assign to
11.3
Milestone
11.3 (Past due)
Assign milestone
Time tracking
None
Due date
None
Reference: gitlab-org/gitlab-foss#48847