Last updated: November 2026
Overview
Keep the board in step with Jira, or request a fresh read when a decision depends on the latest values.
Find the controls
Use Update in the app header for a manual read. The adjacent Update options arrow opens the menu containing Auto Update.
Open Update options to enable Auto Update, or refresh on demand with Update view.
The example shows Auto Update unchecked. The checkbox selects the refresh mode; it is not a freshness indicator.
Choose when to refresh
To request fresh Jira data, select Update in the app header and wait for the request to finish. To enable automatic refresh, open Update options using the adjacent dropdown arrow and tick Auto Update. If changes have not appeared when you need them, use Update again and check that the refresh succeeds.
Board Studio responds to relevant Jira change events by rereading Jira with your permissions. An event signals a possible change; it is not itself the authoritative issue data.
Periodic reconciliation recovers missed events and time-dependent changes, and the app catches up after reconnecting or returning to the foreground. This is not fixed 30-second polling or a guarantee of instant delivery. Changes appear after a successful Jira read; delayed events, connectivity or failed requests can leave an older state visible.
To check a known Jira change, wait for a successful read and inspect that work item’s value on the board or in Inspector. The checkbox shows the chosen mode, not proof that the latest data has arrived.
A checked Auto Update box shows the mode, not proof that new data has arrived.
In this second example, Auto Update is checked. This is the enabled state to look for after reopening Update options. It does not demonstrate a changed Jira value arriving: no Jira records were edited for this capture. If freshness matters now, request a manual Update and verify the value you need after the read completes.
How to Update
The Update Button
The Update button is located in the board’s header bar. It’s a split button with two interaction modes:
| Action | Behaviour |
|---|---|
| Click the button | Requests a fresh read of the current Jira source; wait for it to finish |
| Click the dropdown arrow | Opens a dropdown containing the Auto Update checkbox |
What Happens During an Update
- A loading indicator appears while data is being fetched from Jira
- New issue data is loaded through authenticated app services
- The board automatically re-renders with the updated data
- Cards can move to new positions when refreshed values change their placement
- The Overview section statistics update to reflect the new data
Tip: Click Update after changing Jira work, such as status or assignee, and wait for a successful refresh before treating the board as current.
What Gets Updated
Updates reconcile the current Jira source, including:
| Data Category | What’s Refreshed |
|---|---|
| Issue fields | Status, priority, assignee, summary, labels, components, and all custom fields |
| Issue links | New dependencies, removed links, changed link types |
| Sprint assignments | Issues moved between sprints, new sprint associations |
| Numeric fields | Story points, time estimates, custom number fields |
| New issues | Issues recently created that match your filter or space criteria |
| Removed issues | Issues that no longer match the data source (deleted, moved, or filtered out) |
Refresh Behaviour
Board Studio supports two complementary refresh modes: manual and automatic.
| Aspect | Manual Refresh | Auto Update |
|---|---|---|
| Trigger | User clicks the Update button | Relevant change events, with periodic recovery and reconnection checks |
| Activation | Always available | Enable via the dropdown checkbox |
| Data source | Live Jira data through authenticated app services | Live Jira data through authenticated app services |
| Loading feedback | Visual indicator during data fetch | Visual indicator during data fetch |
| Statistics | Overview section updates after each refresh | Overview section updates after each refresh |
Auto Update: change detection and recovery
Both source types are revalidated through permission-checked Jira reads:
| Data Source | Detection Strategy |
|---|---|
| Project (Space) | Project-scoped change hints trigger reconciliation of the loaded project. |
| Filter | Installation-scoped change hints trigger re-evaluation of the saved filter, including work entering or leaving its results. |
While Auto Update is enabled, a low-frequency Jira reconciliation runs about every five minutes as a recovery measure. Hidden tabs defer work; returning to the foreground catches up when needed. If event delivery is unavailable, reconciliation still provides recovery. Use Update when you need an explicit fresh read rather than waiting for automatic recovery.
Choosing the Right Mode
- Manual refresh lets you choose when to request fresh Jira data, useful during demos, standups and planning sessions.
- Auto Update responds to changes with minimal effort during collaborative sessions. A dashboard widget has its own refresh settings, separate from the full app.
Note: Refreshing Jira data preserves your configured board structure and styling. The refreshed values can change card placement, group membership and dependency lines. Preserving the current configuration is not the same as saving a named board.
If a change has not appeared
Wait for any current load to finish, then use Update to request a fresh read. Check that you are using the intended source and can see the changed work in Jira with the same account. A filter may no longer include an item after its values change.
If the request fails, follow the displayed error rather than treating the existing cards as current. Large sources and slow connections can take longer; see Troubleshooting for loading and access checks.
Tips & Best Practices
| Tip | Details |
|---|---|
| Update after Jira changes | Click Update after changing Jira work, or enable Auto Update for event-driven refresh with periodic recovery |
| Safe during presentations | Disable Auto Update during demos and standups so the board only changes when you click Update |
| Board structure is preserved | Refresh preserves configured swimlanes, link styles, grouping and sorting; changed Jira values can alter their displayed contents |
| Large datasets | Boards with many issues may take a few seconds to refresh; check the loading state before continuing |
| Save configuration separately | Auto Update refreshes Jira data. It does not save unsaved board changes as a named configuration. Use the header’s Save workflow to keep a reusable board |
For the distinction between applying changes to the current view and saving a named configuration, see Managing Configurations.

