Async Field Updates | Sprint Organizer Documentation
Async Field Updates documentation.
Sprint Organizer continuously synchronizes sprint information in the background to keep its dashboards, audit logs, and custom fields up to date without affecting Jira performance.
The synchronization process runs automatically, so no manual action is required.
Synchronization Schedule
The synchronization frequency depends on your license status:
| License Status | Synchronization Frequency |
|---|---|
| Active License | Every 5 minutes |
| Inactive / Expired License | Every 1 day |
Each synchronization scans for changes in tracked sprints and updates the app's internal data accordingly.
What Happens During Synchronization?
During every synchronization cycle, Sprint Organizer:
- Updates all sprint-related custom fields used for JQL searching.
- Detects changes to sprint properties.
- Creates audit log entries for detected changes.
- Refreshes dashboard statistics and sprint metadata.
The synchronization automatically detects changes such as:
- Sprint name changes
- Sprint status changes (Future, Active, Completed)
- Start and end date modifications
- Completion date changes
- Newly created sprints
- Deleted sprints
JQL Custom Fields
Sprint Organizer provides custom fields that can be used in JQL to search and filter issues based on sprint information.
These fields are updated asynchronously during the synchronization process.
This means that if a sprint is renamed, started, completed, or its dates are modified, the corresponding custom field values will not update immediately. Instead, they become available after the next scheduled synchronization.
For example:
- A sprint is renamed at 10:03.
- An active license synchronizes at 10:05.
- The new sprint name is available in JQL searches after the 10:05 synchronization.
Audit Logs
Sprint Organizer keeps a complete history of tracked sprint changes.
Whenever the synchronization detects a modification, an audit log entry is created containing information such as:
- What changed
- Previous and new values
- Who performed the change (when available from Jira)
- Date and time of the change
This provides administrators with a historical record of sprint activity across their Jira instance.
Notes
Changes are not reflected instantly. Sprint Organizer uses asynchronous background synchronization to minimize the impact on Jira performance.
Active licenses receive near real-time updates. With a synchronization interval of five minutes, most sprint changes become available in dashboards, audit logs, and JQL shortly after they are made.
Inactive licenses continue to synchronize once per hour, allowing previously configured environments to remain functional while reducing background processing.