This guide takes you from the welcome screen to a board of Jira work arranged in Status columns. You will inspect a card, then save and reopen the board. No timeline or advanced hierarchy setup is required.
Before you start
Need an explanation along the way? Select the blue question-mark Help button in the header, hover to highlight a teachable region and click it. The Spotlight explains that region without activating its normal action. Escape or an empty-area click leaves the picker; Close or Got it dismisses the explanation. See Guided Tours and Contextual Help.
The first-use tour introduces source type, source selection and Help. After work loads, the next tour covers Overview, General settings, Board structure, Links, Update and Help.
Find the controls
The app header selects the Jira source and saved board. The sidebar arranges that work; the canvas toolbar changes the planning view and opens the Inspector. Each step in this guide shows the relevant controls when you need them.
Ten Frontend Stories appear in To Do, In Progress and Done columns; Rows and Grouping are empty.
This is the completed example you will build below. The source and Save controls are in the header, Status is in the sidebar’s Columns section, and Inspector is at the right of the canvas toolbar.
Overview
Creating your first board involves four steps:
- Select a data source.
- Add Status columns.
- Inspect a card and, where available, a dependency.
- Name, save and reopen the board.
Use one Jira Space or saved Filter throughout. Every screenshot below follows Lea’s Frontend Space in the Northstar Treasury staging dataset: ten Stories from 32 loaded work items across levels. The board uses Status columns with no Rows or Grouping. Your cards and counts will depend on your source.
Step 1: Select a data source
Use the two selectors in the header:
- Choose Space for one Jira project or Filter for a saved JQL filter.
- Open the selector beside it and choose the specific Space or Filter.
- Wait for the cards and links to appear.
Board Studio loads the matching work items automatically. You do not need to select Update for the initial load. Recognise a few expected issue keys or summaries before changing the layout. If you choose Filter, it must already be saved in Jira and accessible to you.
Choose Space, then Frontend. The board is empty until the source loads.
Tip: Start with a Space for a simple team board. Use a Filter when you need cross-project planning or a narrower JQL scope.
Step 2: Configure the board structure
The Board Structure section controls how work is arranged at the active hierarchy level. Select Story in the counted level picker above the canvas, then keep that level unchanged for this task:
- Expand Board Structure in the left sidebar.
- Expand Columns and select its + button, labelled Add dimension: Columns in the tooltip.
- Open the new field selector and choose Status under System fields, not Status category.
Look for status headings across the top or bottom, with cards placed in the matching columns. Columns are vertical bands; Rows are horizontal bands. Leave Rows and Grouping empty for now.
Select Status under System fields for workflow columns.
The completed example at the start of this guide shows To Do, In Progress and Done. Check that cards sit under their current statuses. Try Sprint timelines later with Timeline; other layouts are explained in Board Configuration.
Step 3: Inspect a card
First select one card. Open Inspector → Cards and check its key, summary and available details against the work you expected to load. See Inspector for more ways to inspect a selection.
FRON-40 is selected in In Progress; Inspector shows its key, summary and status.
The example selects FRON-40, Cash position overview widget, in the In Progress column. Inspector shows the same key, summary and status. Rows and Grouping are still empty.
Optional: inspect a dependency
If your source contains blocking dependencies, expand Links in the sidebar. Each discovered link type has independent outward and inward controls. Enable outward blocks for a simple example. Select a visible connection and read its direction and endpoints in Inspector rather than guessing which issue blocks the other. If no such links exist in your source, continue to saving; you do not need to create a dependency for this task.
Choose only the directions that answer your current planning question. See Dependency Links for the illustrated visibility controls and link inspection. You can return later and enable more link types or edit their style.
Step 4: Name and save the board
When the board has unsaved changes:
- Select Save with the plus icon in the header.
- Enter a descriptive board name.
- Select the blue Save button with the checkmark or press Enter. Use Cancel or Escape to leave name entry without saving.
Enter the new board name, then confirm with Save. Name entry alone does not save.
Lea enters a new name containing First Status Board for this same Frontend board. This image shows name entry; the next shows the result after confirming Save and reopening. Use a name appropriate to your board, such as Team work by status.
After confirming, find your name in the header’s saved-board selector and select it to reopen the configuration. Check the source and Status columns. Saving keeps configuration choices, not a frozen copy of Jira work; see Managing Configurations if you need to update or copy the saved view.
In this verified staging example, Lea confirmed Save, reloaded Board Studio and reopened the saved entry containing First Status Board from the selector. The full name, Frontend source, ten Stories and Status columns were restored. Rows and Grouping remain empty. Reloading is a useful persistence check, not a requirement for saving. The new board is private until explicitly shared; no existing board or Jira issue was changed.
After reload, the saved name, Frontend source and Status-column structure are restored.
Next steps
When the basic board is useful, optionally add Priority Rows, then Assignee Grouping, then Created ascending Sorting. Try one change at a time so you can recognise its effect.
- Guided Tours and Contextual Help: explore a control in place when you need it.
- Data Sources: refine the Jira work included on the board.
- Board Configuration: add grouping, sorting, and more dimensions.
- Links: configure visibility, styles, and dependency roll-ups.
- Managing Configurations: rename, share, copy, or delete saved boards.





