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.
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 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 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:
- In the sidebar, expand General Settings
- Find Sorting, which shows the current sorting dimensions
- 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.
- In General settings → Sorting, select the + button, whose tooltip says Add dimension.
- Open the new field selector and choose Created under System fields.
- For this example, remove any other sorting fields using their delete buttons. This makes Created the only ordering rule.
- Hover over the direction button beside Created. If its tooltip says Descending, select it once so it says Ascending.
General settings contains Sorting, separate from Board structure.
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.
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
- Click Add dimension
- Select a Jira field (e.g., Status, Priority, Due Date)
- 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:
- Status (ascending): workflow order.
- Priority (displayed Descending): highest first in the standard priority sequence.
- 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:
- Drag a field by its handle
- Drop it in the new position
- The primary sort is now the topmost field
Removing Sort Fields
- Hover over the sort field row
- Select the remove control
- 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:
- Status (ascending): see To Do items first.
- Priority (displayed Descending): see highest priority first in the standard sequence.
Bug Triage
Sort to see oldest, most severe bugs:
- Priority (displayed Descending): highest priority first in the standard sequence.
- Created (ascending): oldest first.
Story Point Estimation
Sort estimated work from smaller to larger estimates:
- Story Points (ascending): increasing numeric estimates.
- 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.





