Skip to content
GitLab
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
    Projects Groups Snippets
  • Sign up now
  • Login
  • Sign in / Register
  • kanban kanban
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 88
    • Issues 88
    • List
    • Boards
    • Service Desk
    • Milestones
  • Jira
    • Jira
  • Merge requests 4
    • Merge requests 4
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar

Do not update/delete: Banner broadcast message test data

Do not update/delete: Notification broadcast message test data

  • username-removed-97531
  • kanbankanban
  • Issues
  • #119
Closed
Open
Issue created Dec 06, 2015 by username-removed-48087@v.tyubekMaintainer

Cards prioritization

The problem

Cards in columns are ordered simply by id. Many use cases assumes that top cards have higher priority, thus for now cards orders is simply confusing.

The solution

Implement card prioritization in columns.

Implementation details:

The are multiple possible solutions:

  1. we just store priority info in issue content

  2. priorities are stored in kanban own database (redis)

Assignee
Assign to
Time tracking