Why do statuses and priorities appear in that order? Board Studio uses Jira’s field definitions rather than sorting every value alphabetically. Status follows workflow categories; Priority follows Jira’s ranking, not the letters in names such as High and Low.
Find the controls
Open General Settings → Sorting to inspect the ordering fields. The example below has Status followed by Priority. Their ordering icons distinguish workflow order from priority rank. The field order matters: Priority breaks ties between cards with the same Status.
Status follows workflow order; Priority uses Jira rank.
Read the ordering, then check its result
To try Priority on its own, add Priority in Sorting and check the direction control’s tooltip. Displayed Descending normally puts higher priorities first. Compare cards inside the same group or cell; sorting does not move them to a different row or column.
Columns and Rows also use field-aware ordering. The separate Status-column example below shows To Do before In Progress. These workflow headings are not alphabetically ordered: In Progress would otherwise come first.
Status in Columns places work beneath its workflow heading.
Use a dimension’s direction control to reverse its sequence. Grouping does not offer that direction control. For a worked card-ordering example with verified Created dates, see Sorting.
Field-aware ordering
| Field | Ordering |
|---|---|
| Status | Workflow categories, such as To Do, In Progress and Done. |
| Priority | Jira priority rank, with Highest first by default. |
| Issue Type dimensions | Jira hierarchy level first, then names within a level. Higher levels come first by default. |
| Select lists, radio buttons and checkboxes | Administrator-defined option order when available. |
| Dates and date-times | Chronological order. |
| Numbers and estimates | Numeric order. |
| Text, users and projects | Alphabetical order by their displayed values. |
Custom fields are resolved from the site’s metadata. A T-shirt size list configured as XS, S, M, L, XL retains that option sequence instead of becoming alphabetical.
Order Issue Type by hierarchy
An Issue Type dimension no longer follows the project’s issue-type option sequence. With higher levels first, a typical order is Initiative, Epic, then Bug/Story/Task, then Subtask. Types on the same hierarchy level are ordered by name.
The direction control indicates Higher hierarchy levels first or Lower hierarchy levels first. Reverse it to reverse the sequence. Types whose hierarchy cannot be established remain after known levels. An explicitly configured value order takes precedence over automatic ordering.
This is especially useful in Global view, where several hierarchy levels appear together. The field’s name alone is not enough to infer hierarchy; Board Studio uses Jira metadata.
Choose fields with useful coverage
The dimension selector separates System fields and Custom fields and shows field-aware ordering and loaded-data coverage. Coverage is the share of loaded work with a value, not a quality score. A sparsely populated date field can produce a large Unscheduled area.
Reverse direction or combine fields
Use the direction toggle in Columns, Rows or Sorting to reverse its field-aware order. Reversing Status retains workflow semantics; it does not switch to alphabetical status names. For card sorting, add multiple fields and order them by precedence: later fields break ties in earlier ones.
Dimension order has a different purpose: dragging Project above Status changes the nesting of the board’s headers. It does not change Jira’s workflow or field configuration.
Related
- Board Configuration: dimensions, direction controls and card sorting.
- Gantt Timeline: date-bearing dimensions and ancestor placement.

