huminderhuminder
  • Board Studio
  • Blog
  • Contact
  • Menu Menu

Sorting

Last updated: 16 November 2026
See Board Studio on Atlassian Marketplace

Configure how cards are ordered within their groups and swimlane cells.

Overview

Sorting determines the order of cards when they occupy the same board position. You can sort by multiple fields to create a prioritised ordering.

Find the controls

Open General Settings → Sorting in the sidebar. The + adds a sort field. A field’s direction control reverses its order; its handle changes rule precedence; delete removes that rule.

General settings Sorting section with Status followed by Priority, coverage badges, drag handles and direction controls

Sorting fields are separate from the board structure.

These controls order cards within their existing groups or cells. They do not create Columns or Rows or change Jira field values.

See the order without leaving the board

Start with Summary when you want an ordering rule you can check directly on the cards. Add it under General settings → Sorting, leave it as the only sort field, and choose Ascending. Compare cards in the same cell, reading left to right and then down.

Here, three selected Stories share To Do and Medium priority. Focus, using Hide others and Selection only, keeps the example readable. Their summaries run Launch readiness scorecard → Relationship manager handoff for exceptions → Venture-level KPI summary cards.

Summary sorting set to Ascending with focused To Do Medium-priority cards FRON-45 Launch readiness, FRON-39 Relationship manager and FRON-43 Venture-level KPI

Summary ascending: Launch, Relationship, Venture. Read left to right, then down.

Reverse Summary to Descending. The same cards now read Venture → Relationship → Launch. Their Status column and Priority row do not change. This visible reversal is a useful check that the sorting rule is taking effect.

Summary sorting set to Descending with the same focused cards ordered FRON-43 Venture-level KPI, FRON-39 Relationship manager and FRON-45 Launch readiness

Summary descending: Venture, Relationship, Launch. The Status and Priority cell is unchanged.

Focus is only used to simplify these screenshots; it is not required for sorting. Turn it off to return to the wider board. For date-based sorting, use the Created example below and compare the actual dates rather than the summaries.

Accessing Sorting Settings

Sorting is configured in the General Settings section of the sidebar:

  1. In the sidebar, expand General Settings
  2. Find Sorting, which shows the current sorting dimensions
  3. Use the controls to add, remove, or reorder sort fields

For a first example, keep your Status Columns, Priority Rows and Assignee Grouping. These are view settings, not changes to Jira’s field values.

  1. In General settings → Sorting, select the + button, whose tooltip says Add dimension.
  2. Open the new field selector and choose Created under System fields.
  3. For this example, remove any other sorting fields using their delete buttons. This makes Created the only ordering rule.
  4. Hover over the direction button beside Created. If its tooltip says Descending, select it once so it says Ascending.
General settings Sorting field selector open on System field Created with 100 percent coverage, above Work item created forms

General settings contains Sorting, separate from Board structure.

Sorting dimension Created with 100 percent coverage and the direction button showing the Ascending tooltip

The direction tooltip confirms Ascending for Created.

Compare cards that share a group or swimlane cell: earlier creation dates come before later ones. If each position contains only one card, there may be no visible change. Sorting does not move a card into a different Status column or Priority row.

Marcus Weber group with BAC-2 at upper left, BAC-5 at upper right and BAC-7 below, while Created Ascending is configured

Created ascending gives BAC-2, BAC-5, then BAC-7 in reading order.

In this example, read left to right, then down: BAC-2 → BAC-5 → BAC-7. Their loaded Created values are 20 September 2026 at 15:07:52, 15:08:03 and 15:08:12, respectively, in the source’s UTC+02:00 timezone. These timestamps were checked in the loaded Jira data; they are not printed on the pictured cards. Reversing the direction was also checked: BAC-7 → BAC-5 → BAC-2. For your own board, compare the Created values in Jira if the cards do not display them.

Adding Sort Fields

  1. Click Add dimension
  2. Select a Jira field (e.g., Status, Priority, Due Date)
  3. Configure the sort direction

Cards are sorted by the first field, then by subsequent fields for ties.

Sort Direction

Each sort field can be ordered:

Direction Behaviour
Ascending A to Z for text, smaller to larger for numbers, or earlier to later for dates. Status, Priority and configured option fields follow their own Jira-aware ordering. For Priority, the displayed ascending direction puts lower priorities first.
Descending Z to A, larger to smaller numeric values, or later to earlier dates. For Priority, the displayed descending direction puts higher priorities first.

Use the direction control and its tooltip to toggle. Priority uses Jira’s priority ranking rather than alphabetical order: the displayed Descending setting normally gives Highest, High, Medium, Low, Lowest. Follow the displayed label, not an internal configuration value. See Business Logic Detection for field-ordering reference.

Multi-Field Sorting

Add multiple fields to create compound sorting:

Example:

  1. Status (ascending): workflow order.
  2. Priority (displayed Descending): highest first in the standard priority sequence.
  3. Created (ascending): oldest first.

Cards are first sorted by Status. Cards with the same Status are then sorted by Priority. Cards with the same Status and Priority are sorted by Created date.

Business Logic Detection

Board Studio automatically detects how fields should be sorted:

Field type Detected logic Sort behaviour
Status Workflow To Do → In Progress → Done
Priority Priority Displayed Descending follows highest to lowest priority; displayed Ascending reverses it.
Due Date Date Chronological order
Story Points Numeric Numerical order
Assignee Alphabetical A→Z order
Custom select Option Configured option order

The detected ordering strategy determines what ascending means for each field. Check the field’s ordering information when a custom Jira configuration uses a different sequence.

Default Sorting

When no sorting is configured:

  • No default dimensions are applied
  • Users must manually add sorting fields via the Add Dimension button
  • Cards appear in the order returned by the layout algorithm

Reordering Sort Fields

Change the priority of sort fields:

  1. Drag a field by its handle
  2. Drop it in the new position
  3. The primary sort is now the topmost field

Removing Sort Fields

  1. Hover over the sort field row
  2. Select the remove control
  3. The field is removed from sorting

Sorting and Layout

Sorting affects card arrangement within the graph layout:

  • Cards in the same group or swimlane cell are positioned according to sort order
  • The layout algorithm respects sort order when placing cards
  • Changing sort order triggers a smooth 800ms layout animation

Examples

Sprint Planning Board

Sort to see incomplete work by priority:

  1. Status (ascending): see To Do items first.
  2. Priority (displayed Descending): see highest priority first in the standard sequence.

Bug Triage

Sort to see oldest, most severe bugs:

  1. Priority (displayed Descending): highest priority first in the standard sequence.
  2. Created (ascending): oldest first.

Story Point Estimation

Sort estimated work from smaller to larger estimates:

  1. Story Points (ascending): increasing numeric estimates.
  2. Priority (displayed Descending): highest priority first when estimates tie.

Missing Story Points are not converted to zero. The numeric ordering strategy treats missing or non-numeric values as unknown, using a high sort value. For ordinary story-point ranges, they follow populated estimates in ascending order and move before them when the order is reversed. Do not use “unestimated (0) first” as an interpretation of ascending sorting.

What's Next?

  • Grouping: stack related cards together.
  • Links: configure dependency visualisation.

Board Studio for Jira Cloud®

  • Overview
    • Getting started
      • Installation
      • Your First Board
      • Key Concepts
    • User Guide
      • Global App Interface
      • Data Sources
      • Board Configuration
        • Working with dimensions
        • Rows
        • Columns
        • Grouping
        • Sorting
      • Dependency Links
      • Managing Configurations
      • Jira Dashboard Widget
      • Settings
      • Sharing Configurations
    • Features
      • Jira Dependency Graph
      • Focus Mode
      • Semantic Zoom
      • Gantt Timeline
      • Card Avatars
      • Rollups
      • Business Logic Detection
      • Auto Update
      • Export
      • Localisation & Themes
      • Guided Tours and Contextual Help
      • Inspector
      • Search
      • Navigation History
      • Parent Context
      • Family Cards and Hierarchy
      • Global View
      • Board Insights
    • FAQ
    • Troubleshooting
    • Support
      • Data Security and Privacy Statement
      • Data Processing Agreement
      • Source Code Licence
      • End User Licence Agreement

Company

Human-led delivery for the AI era.
Contact

Product & Docs

Product

  • Board Studio for Jira Cloud
  • Atlassian Marketplace listing
  • Video library

Documentation

  • Documentation overview
  • Getting started
  • User guide
  • Features
  • FAQ
  • Troubleshooting
  • Support

Legal & Trust

  • Privacy Policy
  • Trust Center
  • SLA
© Copyright huminder 2026, all rights reserved.
  • Link to LinkedIn
  • Link to X Link to X Link to X
  • Link to Youtube
Scroll to top Scroll to top Scroll to top

Customize

Essential Functions

Analytics