Skip to content

GitLab Next

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 43,035
    • Issues 43,035
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,358
    • Merge requests 1,358
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • GitLabGitLab
  • Issues
  • #979
Closed
Open
Created Sep 07, 2016 by Mark Pundsack@markpundsackContributor

Issue board swimlanes

Description

When the number of open issues grows, adding another sorting view becomes necessary and swimlanes are a common solution. Being able to group issues by Priority or Milestone or User or Team (label) and show them in their workflow stage is a very common practice when the number of issues flows off the screen.

Proposal

Add another dimension to the issue boards so in addition to vertical lists, there are horizontal swimlanes. Swimlanes can divide issues up by:

  • Priority
  • Milestone
  • User
  • or specific labels

The existence of swimlanes may allow more complex issue board types (https://gitlab.com/gitlab-org/gitlab-ee/issues/977) or may simply be an orthogonal feature to layer on existing types.

Links / references

  • Suggestion by @dhekimian in https://gitlab.com/gitlab-org/gitlab-ce/issues/17907#note_12940204
  • Builds on https://gitlab.com/gitlab-org/gitlab-ee/issues/977

/cc @JobV

Assignee
Assign to
Time tracking