Jira Data Refresh Frequency Across LinearB Reports
Learn how often Jira data is collected, processed, and reflected across LinearB reports, including Pulse, Progress Over Time, Resource Allocation, Investment Strategy, and Project Delivery Trackers.
Learn how often Jira data is collected, processed, and reflected across LinearB reports, including Pulse, Progress Over Time, Resource Allocation, Investment Strategy, and Project Delivery Trackers.
Overview
LinearB regularly collects data from Jira and processes it before displaying the latest information in reports and dashboards. Because some reports require additional processing, changes made in Jira may not appear immediately or at the same time across every LinearB report.
The total refresh time depends on:
- The Jira data collection schedule.
- The processing required by the report.
- The size and complexity of your organization.
- Whether the report refreshes on a schedule or in response to an event.
Jira Report Refresh Frequency
Report or process | Refresh frequency | Expected availability |
Jira data collection | Every hour | Collection typically takes approximately 20–30 minutes. |
Jira data processing pipeline | Every hour | Processing typically takes approximately 30–40 minutes after collection. |
Pulse | After each Jira collection job | New Jira data generally appears within approximately one hour. |
Project Delivery Tracker | Triggered by events such as the end of an iteration or a configuration change | Processing typically takes approximately 30 minutes after the required Jira data is available. Allow up to approximately two hours for changes to appear. |
Progress Over Time: project data | Daily | Updated at approximately 4:30 AM UTC. |
Progress Over Time: insights | Every four hours | Insight processing runs in scheduled batches around the hour and half-hour. |
Resource Allocation | Daily | Processing runs at approximately 6:00 AM and 6:30 AM UTC. Data may take an additional 10–30 minutes to appear, depending on organization size. |
Investment Strategy | Daily | Updated after the daily allocation processing completes. |
Custom reports | Depends on the underlying data source | Reports using Jira data reflect updates after the relevant collection and processing jobs complete. |
Understanding Refresh Times
A report’s refresh frequency is not always the same as the Jira collection frequency. LinearB may first need to collect the Jira data and then run one or more processing jobs before the updated information appears.
For example, a change made in Jira shortly after an hourly collection begins may not be included until the next collection. The collected data may then require additional pipeline or report-specific processing.
As a result, two LinearB reports that use the same Jira issue may display the update at different times.
Configuration Changes
Some reports may refresh when their settings change. Changes to report scope, Jira boards, filters, allocation rules, or other configuration settings can trigger additional processing.
After changing a report’s configuration, allow the associated processing job to complete before validating the updated results.
Troubleshooting Delayed Jira Data
If recently updated Jira data does not appear in LinearB:
- Confirm that the issue is included in the connected Jira board or project.
- Verify that the issue matches the report’s configured scope and filters.
- Allow enough time for Jira collection and report-specific processing to complete.
- Refresh the LinearB page after the expected processing window.
- Check whether a recent configuration change triggered additional processing.
Processing can take longer than the estimates above for large organizations or workspaces containing significant amounts of Jira data.
If the data remains outdated after the expected refresh window, please contact LinearB Support.
How did we do?
Dashboards & Reporting
Metrics Builder
