Use the configuration sidebar to arrange Jira cards by fields such as Status and Priority. Changes appear on the board as you make them; save the configuration separately when you want to keep it.
Find the controls
Use Board Structure in the sidebar for Columns, Rows, Grouping and Cards layout. Choose the planning level before editing its structure. General Settings → Sorting orders cards within that structure.
The active Epic structure uses Sprint Columns and Project Rows.
Each section’s + adds a dimension. The controls beside a field change that dimension; the later Dimension controls reference explains each one.
Build a first view
For a first result, load a source, expand Board Structure → Columns, select Add dimension and choose Status. Look for status headings and matching cards. Select a card and inspect it, then save and reopen the board. That is enough for a useful first view.
Use the Columns + button, then choose the System field Status.
Add dimension is the section’s + button. Choose Status under System fields. The Columns walkthrough shows the result and explains how to change or remove it.
Optionally continue with Priority in Rows, Assignee in Grouping, then Created ascending in General Settings → Sorting. The examples below demonstrate other arrangements, not consecutive stages of this task.
Each cell combines a Status column and a Priority row.
This optional matrix combines Status Columns with Priority Rows. Use the child guides above for the individual controls; the reference below covers more advanced arrangements.
Overview
Open the configuration sidebar by clicking Expand sidebar in the header bar. The sidebar slides in from the left with two main sections:
| Section | Purpose |
|---|---|
| Board Structure | Define swimlanes, card grouping, and linked-card separation for each hierarchy level |
| General Settings | Define the order of cards within each board cell |
Board, Polar and Hierarchy control card placement inside the board structure.
💡 Tip: Start simple. Add one dimension, see the result, then layer in more. You can always remove dimensions you don’t need.
Board Structure
The Board Structure section controls the visual grid of your board. Its dimension subsections each add a different type of spatial organisation. Select the active level or Global view on the canvas before editing its structure.
Dimension types
| Dimension type | Creates | Headers appear at | Axis | Visual result |
|---|---|---|---|---|
| Rows | Horizontal bands | LEFT and RIGHT edges | Y-axis | Issues split into rows |
| Columns | Vertical bands | TOP and BOTTOM edges | X-axis | Issues split into columns |
| Grouping | Card groups within cells | Inline group headers | Within cells | Cards stacked under collapsible headers |
Cards layout inside cells
Choose Board, Polar or Hierarchy for card placement. Polar arranges cards radially within the Cartesian regions defined by Columns and Rows. It does not turn the whole board into a circular coordinate system or rename the axes to Sectors and Rings. Columns, Rows, grouping and timelines keep their existing roles.
Polar keeps Sprint Columns and Team Rows; it does not create sectors or rings.
Visual examples
Sprint (columns) × Project (rows)
Use Columns for Sprint and Rows for Project. The result is a portfolio grid that lets you compare delivery periods across projects at a glance.
The Story grid groups delivery periods by project without timeline placement.
Adding Priority grouping within cells
Add Priority under Grouping to organise cards beneath collapsible priority headers inside each grid cell. This makes urgent work easier to identify without changing the board’s rows or columns.
Priority grouping is nested inside Project Rows and the Sprint timeline.
Nested swimlanes (Project → Status rows)
Add Project, then Status, under Rows to subdivide every project row by workflow stage. This keeps project ownership visible while exposing where work is accumulating.
Project followed by Status subdivides each project by workflow stage.
Dimension controls
Each dimension row combines the selected Jira field with controls for its position and ordering. The field’s icon identifies the ordering logic Board Studio detected from Jira metadata, while the percentage badge shows how many loaded work items contain a value for that field.
Drag, ordering, coverage, timeline, direction, header side and removal stay beside each field.
Control reference
| Control | Icon | Action | Available on |
|---|---|---|---|
| Drag handle | ⠿ (6 dots) | Reorder dimensions via drag-and-drop | All dimension types |
| Field selector | Dropdown | Choose any Jira system or custom field | All dimension types |
| Sort direction | ↑ / ↓ | Toggle ascending or descending order | Swimlanes |
| Header position | ◁ / ▷ or △ / ▽ | Toggle header position (Left/Right or Top/Bottom) | Swimlanes |
| Visibility toggle | 👁 | Show/hide specific field values | All dimension types |
| Delete | ✕ | Remove the dimension from the board | All dimension types |
The ordering icon and direction work together. For example, Status uses workflow order, Priority uses Jira priority rank (and defaults to Highest first), and Due date uses chronological order. The arrow reverses that field-aware sequence; it does not replace it with alphabetical sorting.
Issue Type dimensions use Jira hierarchy level first and peer names within a level. Their direction control chooses higher or lower hierarchy levels first, rather than following the project’s issue-type option sequence.
Timeline controls and ancestor placement
Use Switch to timeline on an eligible date-bearing dimension. Its timeline settings appear beneath that active dimension; replacing the field resets its timeline mode. Under Timeline placement, Use ancestor dates for undated cards places a card lacking dates using the nearest loaded ancestor with dates for the same field, independently per timeline axis. It does not change Jira dates or the child’s duration. Without suitable dates, the card remains Unscheduled.
See Gantt Timeline for placement and two-axis behaviour. Global view supports one active timeline axis at a time.
Adding a dimension
- Expand the subsection (Rows, Columns, or Grouping).
- Click Add Dimension at the bottom of the subsection.
- Select a Jira field from the dropdown.
- The board updates immediately with the new dimension applied.
System field options show their ordering type and loaded-data coverage.
The selector separates System fields from Custom fields when available. The screenshot shows the System fields portion of the list; it does not show the Custom fields category. Every row includes:
- the Jira field name;
- an ordering icon such as Workflow, Priority, Date, Numeric, Options, or Alphabetical;
- a coverage percentage showing the share of loaded work items with a value.
Prefer fields with meaningful coverage for the current data source. A low percentage is valid, but it creates a large empty or unscheduled bucket.
Reordering dimensions
When multiple dimensions exist in the same subsection, their order determines the nesting hierarchy:
- Grab the drag handle (⠿) on the left of the dimension row.
- Drag to the desired position.
- Drop to lay out the board with the new hierarchy.
💡 Tip: The first dimension in a swimlane list is the outermost level. Drag the most important grouping to the top.
Removing a dimension
- Click the delete button (✕) on the right of the dimension row.
- The dimension is removed and the board updates immediately.
Field discovery
The fields available in dimension selectors depend on the loaded data:
| Field category | Availability |
|---|---|
| System fields (Status, Priority, Sprint, Assignee, etc.) | Always available |
| Custom fields (Story Points, Team, RACI Role, etc.) | Discovered from loaded issues |
| Multi-project fields | Union of all fields across loaded projects |
📝 Note: If a custom field doesn’t appear in the dropdown, ensure the issues using that field are loaded via your data source. Fields are discovered dynamically: they appear once Board Studio sees at least one issue containing them.
Business Logic Detection
Board Studio automatically detects the semantic meaning of each field and applies intelligent sort defaults. A small icon appears next to each dimension to indicate the detected ordering type.
Status follows workflow order; Priority uses Jira rank.
Ordering type reference
| Icon | Ordering type | Fields | Default behaviour |
|---|---|---|---|
| ⚙️ | Workflow | Status | Follows workflow sequence: To Do → In Progress → Done |
| ⬆️ | Priority | Priority | Ranked by importance: Highest → Lowest |
| 📅 | Chronological | Date, Created, Updated, Due Date, Sprint | Ordered by time |
| 📊 | Numerical | Story Points, Number fields | Ordered by numeric value |
| 🔤 | Alphabetical | Text, User, Project | Locale-aware A → Z sorting |
| ••• | Option-based | Select lists, Radio buttons, Checkboxes | Follows Jira admin option order |
How detection works
- When you add a field as a dimension, Board Studio analyses its Jira schema metadata.
- The system classifies the field into one of the ordering types above.
- An appropriate default sort direction is set automatically (e.g., Priority defaults to descending for “Highest first”).
- The icon is displayed on the dimension row.
You can always override the default direction using the sort direction toggle (↑/↓).
💡 Tip: For custom select fields (like “Environment” or “RACI Role”), Board Studio uses the option order defined in Jira administration, not alphabetical order. This means the sort will match the sequence your Jira admin configured.
Live preview
Every configuration change triggers an immediate visual update on the board.
| Aspect | Detail |
|---|---|
| Animation duration | Smooth morphing transition (typically 800ms for full layout changes, 500ms for incremental updates) |
| What animates | Cards flow to new positions, headers appear/disappear, groups expand/collapse |
| No reload required | All updates happen in-place without page refresh |
| Undo-friendly | Change your mind? Modify or remove the dimension and the board morphs back |
Status creates workflow subrows inside each Project Row.
📝 Note: During layout animations, the data source selector and Update button are temporarily disabled to prevent conflicting operations.
Unlimited nesting
Swimlane subsections support unlimited nesting of dimensions. Each added dimension creates a deeper level of board structure.
| Nesting level | Example (Rows) | Result |
|---|---|---|
| 1 dimension | Project | One row per project |
| 2 dimensions | Project → Assignee | Rows subdivided by assignee within each project |
| 3 dimensions | Project → Assignee → Priority | Further subdivided by priority within each assignee |
The header area expands to accommodate multi-level nesting with indented labels.
⚠️ Warning: While there’s no hard limit, deeply nested layouts (4+ dimensions) can become visually dense. Two to three dimensions per axis typically provides the best balance of structure and readability.
Separate linked cards
Use Separate linked cards in Board Structure to distinguish dependency chains from standalone work at the active hierarchy level.
With the option disabled, linked and standalone cards share the same grid area. This compact view works well when you want to scan all work together.
Separate linked cards is off on this Story grid.
Enable the option to place dependency chains in a dedicated zone above the standalone cards. Connections become easier to trace without losing the surrounding work context.
Separate linked cards is on at Story level.
| State | Effect |
|---|---|
| Enabled | Linked cards appear in a dedicated dependency zone above standalone work |
| Disabled (default) | Linked and standalone cards appear together in the same grid area |
📝 Note: Board Structure settings apply to the hierarchy level currently selected in the toolbar. Configure each level independently when you want different layouts for Stories, Epics, or higher-level work.
General Settings
Use Sorting in General Settings to control the order of cards within each swimlane cell. Add several fields when you need a predictable sequence for planning or review.
Sorting fields are separate from the board structure.
How multi-field sorting works
Cards are sorted by multiple fields in priority order:
| Sort rank | Field | Direction | Meaning |
|---|---|---|---|
| Primary | Status | ↑ Ascending | To Do → In Progress → Done |
| Secondary | Priority | ↓ Descending | Highest → Lowest |
| Tertiary | Assignee | ↑ Ascending | Alice → Bob → Carol |
Ties in the primary field are broken by the secondary field, then the tertiary, and so on.
Sort controls
Sort dimensions use the following controls; Grouping has different expand/collapse controls:
| Control | Action |
|---|---|
| Drag handle (⠿) | Reorder sort priority |
| Field selector | Choose the Jira field to sort by |
| Direction toggle (↑/↓) | Switch ascending / descending |
| Delete (✕) | Remove this sort field |
| Add Dimension | Add another sort field at the bottom |
Direction toggle behaviour
| Direction | Icon | Meaning |
|---|---|---|
| Ascending | ↑ | A→Z, 1→9, To Do→Done, Low→High, oldest→newest |
| Descending | ↓ | Z→A, 9→1, Done→To Do, High→Low, newest→oldest |
Note: Priority uses inverted semantics: Highest has the lowest internal rank in Jira. Board Studio handles this automatically, so ↑ means Low→High and ↓ means High→Low.
Empty state
When no sort dimensions are configured, no explicit card sort is applied; placement is determined by the layout. The subsection displays:
- “No sorting configured”
- “Click ‘Add Dimension’ to define sort order”
Configuration workflow summary
Here’s the recommended workflow for setting up a board from scratch:
| Step | Action | Section |
|---|---|---|
| 1 | Select a data source (Space or Filter); its issues load automatically | Header bar |
| 2 | Click Expand sidebar | Header bar |
| 3 | Add Status under Columns and inspect a card | Board Structure / Inspector |
| 4 | Optionally add Priority under Rows | Board Structure |
| 5 | Optionally add Assignee under Grouping | Board Structure |
| 6 | Adjust dimension nesting and, for Columns or Rows, direction as needed | Board Structure |
| 7 | Toggle Separate linked cards when you want a dedicated dependency zone | Board Structure |
| 8 | Optionally add Created ascending to Sorting | General Settings |
| 9 | Name, save and reopen the configuration | Header bar |
💡 Tip: Board Studio saves configurations so you can switch between different board layouts instantly. Create a “Sprint Planning” config and a “Portfolio Overview” config for the same data source.
Next steps
- Data Sources: select and manage the data powering your board.
- Features: explore dependency visualisation, Global view, hierarchy and timelines.














