Board Studio connects to your Jira data through data sources, the starting point for every board. Choose what work items to visualise, and Board Studio handles the rest.
Overview
A data source defines which Jira issues appear on your board. Board Studio supports two types:
| Data source type | What it pulls | Best for |
|---|---|---|
| Space (Project) | All issues from a single Jira project | Team-level boards focused on one project |
| Filter (Saved filter) | Issues matching a JQL query | Cross-project planning, portfolio views, custom scopes |
💡 Tip: Start with a Space for quick setup. Move to Filters when you need cross-project visibility or tighter scope control.
Find the controls
Use the two selectors in the app header: the first chooses Space or Filter; the second chooses the specific source. These selectors define the Jira work to load, not its visual arrangement.
Choose Space or Filter before selecting its value.
Selecting a data source
Data source selection happens in the header bar at the top of the app, using two dropdown selectors side by side.
Before choosing Filter, save the filter in Jira or ask its owner to share it with you. For a first board, choose a Space containing work you recognise. Loading a source already creates a board; columns, rows and grouping are optional ways to organise it afterwards.
Step 1: Choose the data source type
- Click the type selector dropdown on the left side of the header bar.
- Select either Space or Filter.
The type selector is disabled while issues are loading or a layout is in progress to prevent conflicting operations.
Step 2: Choose a specific data source
- Click the data source selector dropdown (to the right of the type selector).
- Browse the list or type to search. The dropdown filters results as you type.
- Click the desired project or filter to select it.
- Issues load automatically; no additional action is needed.
Check a few familiar issue keys or summaries on the board. Overview in the sidebar reports the loaded work and links. If expected work is absent, check the source in Jira and your access before changing the layout.
📝 Note: The data source selector adapts its placeholder text based on the selected type, showing “Select a space…” or “Select a filter…” accordingly.
Working with Spaces
When Space is selected, the dropdown lists all Jira projects you have access to.
| Feature | Behaviour |
|---|---|
| List contents | All Jira projects visible to the current user |
| Search | Type to filter by project name |
| Project avatars | Each project shows its Jira avatar icon |
| Scope | All issues within the selected project |
What gets loaded
Selecting a Space loads all issues from that Jira project, respecting the project’s issue hierarchy:
- Epics (and higher-level items)
- Stories, Tasks, Bugs
- Sub-tasks
Working with Filters
When Filter is selected, the dropdown lists your saved Jira filters, organised into two groups.
Filter list organisation
| Group | Icon | Contents |
|---|---|---|
| Favourites | ⭐ Star | Filters you’ve starred in Jira |
| Other Filters | No star | Your remaining saved filters |
Favourite filters appear first for quick access. The star indicator (⭐) matches your Jira favourites. Star or un-star filters in Jira to control what appears in that group.
Cross-project data
Saved filters choose precisely which Jira work to load, from one project or several.
A single JQL filter can pull work items from multiple Jira projects onto one board. For example:
project IN (FRON, BAC, MOB) AND sprint IN openSprints()
This creates a unified view across Frontend, Backend, and Mobile teams, showing all their active sprint work and the dependencies between them.
💡 Tip: Configure the saved filter’s sharing permissions in Jira so colleagues can use it as a Board Studio data source. Filter subscriptions send notifications; they do not grant access. Colleagues also need permission to view the matching Jira issues. Sharing a Board Studio configuration does not grant either permission.
Loading issue data
When you select a data source, Board Studio automatically loads the matching issues; there is no separate “load” step.
How it works
- You select a data source (Space or Filter).
- Board Studio sends an authenticated request to Jira.
- Issues matching the data source are fetched with all their fields and links.
- The board populates with the loaded data.
- Dependency links between issues are resolved and displayed.
Refreshing data with the Update button
The Update button in the header bar lets you manually refresh the issue data already on the board. Use it when the underlying Jira data has changed and you want to pull the latest state.
| Scenario | When to use Update |
|---|---|
| Issues changed in Jira | Someone updated a status, priority, or assignee |
| New issues created | Issues were added to the project or filter scope since the board loaded |
| Links modified | Dependencies were added or removed in Jira |
| Sprint changes | Items were moved between sprints |
💡 Tip: Open Update options beside the Update button and enable Auto Update for event-driven refresh with periodic recovery of missed changes. This is not fixed 30-second polling. See Auto Update for details.
Boundary links
Overview → Boundary links counts Jira relationships with one endpoint outside the dataset, including inward and outward references, not distinct external work items. A boundary count does not automatically load those endpoints or prove they are accessible. Expand the saved filter deliberately when both sides of a dependency belong in the planning scope; Jira permissions still apply.
Overview separates loaded work items, links and boundary links.
Space vs. Filter comparison
| Criteria | Space (Project) | Filter (Saved JQL) |
|---|---|---|
| Scope | Single Jira project | Any saved JQL query, single or multi-project |
| Setup complexity | Select a project | Requires a saved Jira filter with JQL |
| Cross-project | ✗ Single project only | ✓ Combine issues from multiple projects |
| Issue control | All issues in the project | Fine-grained JQL-based scoping |
| Best for | Team boards, project-level views | Programme boards, portfolio views, PI planning |
| Dependency visibility | Dependencies within the project | Dependencies across all included projects |
| Filter maintenance | None; refresh to load current work | JQL filter must be maintained in Jira |
Performance recommendations
Board Studio handles large datasets, but performance varies with the number of issues loaded.
There is no guaranteed response time based only on issue count. Link density, layout, browser and device also matter. Prefer a saved filter scoped to the planning decision rather than loading an entire large project.
Whole-source AI analysis has a separate limit of 200 accessible work items. See Board insights for analysis scope and evidence limits.
Tips for large datasets
- Use filters to scope: Instead of loading an entire project, create a JQL filter targeting specific sprints, components, or labels.
- Focus on active work:
sprint IN openSprints()limits data to active sprints; includefutureSprints()separately if you also need planned sprints. - Leverage components:
component = "Platform"narrows to a specific team’s work. - Combine criteria:
project IN (FRON, BAC) AND sprint IN openSprints() AND statusCategory != Donegives you active cross-project work without closed items.
Important: Keep the loaded scope relevant and manageable. A smaller source can reduce the work needed to load and lay out the board, but issue count alone does not guarantee that one board will be faster than another.
Jira permissions
Board Studio respects Jira’s permission model at every level.
| Permission aspect | Behaviour |
|---|---|
| Project visibility | Only projects you can access appear in the Space list |
| Filter visibility | Only filters you own or have been shared with you appear |
| Issue-level security | Issues you cannot view in Jira are excluded from the board |
| Field-level security | Restricted fields are not displayed on cards |
Every Jira request is made on behalf of the logged-in user and respects their exact Jira permissions. No admin credentials are used, and no data is accessible beyond what the user can see in Jira itself.
📝 Note: If issues seem to be missing from your board, check your Jira permissions first. Board Studio cannot show issues that Jira restricts from your account.
Next steps
Once your data source is selected:
- Board Configuration: organise your board with swimlanes, grouping and sorting.
- Features: explore dependency visualisation, Focus mode, semantic zoom and more.
- Guided Tours and Contextual Help: activate Help and choose either source selector for an explanation without changing the source.

