Field Updates | Sprint Organizer Documentation

Field Updates documentation.

Sprint Organizer keeps sprint data, custom fields, dashboards, and audit logs up to date automatically in the background.

Updates are processed using a combination of Jira events and scheduled background synchronization. The update method depends on the type of change and whether Sprint Organizer has an active license.

No manual action is required.

Update Schedule

Different types of changes are processed at different times.

Updates described as Immediately are triggered by Jira events and processed by Sprint Organizer as soon as the corresponding event is received.

Updates described as Within 5 minutes are handled by background synchronization.

Sprint Changes

With an Active License, changes to existing sprints are processed using Jira events.

This includes changes such as:

• Sprint Name
• Sprint Goal
• Sprint State
• Sprint Start Date
• Sprint End Date
• Sprint completion
• Issue movement between sprints

When Jira sends the corresponding event, Sprint Organizer processes the change and updates the affected Sprint Reporting fields without waiting for the next scheduled synchronization.

With the Free version, these changes are processed by background synchronization and may take up to 5 minutes to appear.

Issue Movement Between Sprints

When an existing issue is moved between sprints, Sprint Organizer needs to update both its current sprint information and its sprint history.

With an Active License, issue movement is detected through Jira events and the corresponding Sprint Reporting fields are updated immediately.

With the Free version, issue movement is detected and processed within 5 minutes.

This includes updates to fields used for current and historical sprint reporting, such as Sprint Name, Sprint State, Closed Sprints, and All Sprints, where applicable.

New Issues Created in a Sprint

Creating a new issue directly inside a sprint is handled differently from moving an existing issue between sprints.

For both Active License and Free versions, Sprint Organizer processes newly created issues through background synchronization.

Sprint Reporting fields for a newly created issue may therefore take up to 5 minutes to be populated.

Board Changes

Changes to Scrum boards are processed through background synchronization for both license types.

This includes:

• Board name changes
• Board deletion

These changes may take up to 5 minutes to be reflected in Sprint Organizer and related Sprint Reporting fields.

JQL Custom Fields

Sprint Organizer provides Sprint Reporting custom fields that can be used in JQL, filters, dashboards, reports, and automations.

The time required for a custom field value to reflect a Jira change depends on the type of change.

With an Active License, supported sprint changes and issue movements are processed immediately through Jira events.

Other changes, such as newly created issues and board changes, are processed within 5 minutes.

With the Free version, Sprint Reporting field updates are processed within 5 minutes.

Because updates are asynchronous, there may be a short period during which Sprint Reporting fields still contain the previous values.

Audit Logs

Sprint Audit Logs are event-driven for both Active License and Free versions.

When Sprint Organizer receives a supported Jira sprint event, the corresponding audit information is processed immediately without waiting for the scheduled 5-minute synchronization.

Audit logs can record changes such as:

• Sprint creation
• Sprint deletion
• Sprint name changes
• Sprint goal changes
• Sprint state changes
• Start and end date changes
• Sprint completion

Where available, audit entries can also include information about who performed the change, previous and new values, and the date and time of the event.

Why Are Some Updates Delayed?

Not every Jira operation produces the same type of event or provides all the information required to update Sprint Organizer immediately.

For this reason, Sprint Organizer combines event-driven updates with scheduled background processing.

The 5-minute synchronization ensures that changes not handled immediately through Jira events are still detected and reflected in Sprint Organizer.

Notes

• Active License provides immediate event-driven updates for supported sprint changes and issue movement between sprints.
• Free processes these sprint and issue movement changes within 5 minutes.
• New issues created inside a sprint are processed within 5 minutes for both license types.
• Board name changes and board deletions are processed within 5 minutes for both license types.
• Sprint Audit Logs are processed from Jira events immediately for both license types.
• All update processes run automatically in the background and do not require Sprint Organizer to remain open.

Related Pages

• Sprint Reporting & JQL
• Fields Overview
• Sprint Audit Log
• Deleted Sprint Tracking
• Permissions Settings
• Licensing