Licensing | Sprint Organizer Documentation
Licensing documentation.
Sprint Organizer can be used with an Active License or as the Free Edition.
Both editions provide sprint tracking, Sprint Reporting fields, JQL support, dashboards, and audit logs. The main differences are:
- How many Scrum boards are tracked
- Which sprints and work items are included
- How quickly supported changes are processed
Free Edition vs Active License
| Feature | Active License | Free Edition |
|---|---|---|
| Tracked boards | All accessible Scrum boards | Up to 3 selected Scrum boards |
| Board selection | Automatic | Configured manually by an administrator |
| Tracked sprints | Sprints from all accessible Scrum boards | Sprints whose origin board is selected |
| Tracked work items | All Work items | Work items that belong to the space associated with the selected board |
| Supported sprint changes | Processed immediately from Jira events | Processed within 5 minutes |
| Work items moved between sprints | Processed immediately from Jira events | Processed within 5 minutes |
| New work items created in a sprint | Processed within 5 minutes | Processed within 5 minutes |
| Board changes | Processed within 5 minutes | Processed within 5 minutes |
| Sprint Audit Log events | Processed immediately from Jira events | Processed immediately |
| Orphan Sprints | Available | Not available |
All updates run automatically in the background. Sprint Organizer does not need to remain open.
Active License
With an Active License, Sprint Organizer automatically tracks all Scrum boards that it can access in Jira. Administrators do not need to select boards manually.
Sprints and associated work items from the tracked boards are included in Sprint Organizer features, including:
- Dashboards and reports — information is generated using sprints and work items from all accessible Scrum boards
- Sprint Reporting custom fields — synchronized sprint data can be displayed on work items and used by Jira features
- JQL fields — sprint information can be used in Jira searches, filters, dashboards, reports, and automations
- Sprint Audit Logs — supported sprint events are recorded immediately after Sprint Organizer receives them from Jira
- Deleted sprint tracking — synchronized sprints that later disappear from Jira can be retained as deleted sprint records
- Orphan Sprints — sprints whose origin boards no longer exist can be found, reviewed, assigned to another board, or deleted
Supported changes to existing sprints and work item movement between sprints are processed immediately after Sprint Organizer receives the corresponding Jira event.
Access to board, sprint, space, and work item information still depends on Jira permissions and the Sprint Organizer Permissions.
Free Edition
With the Free Edition, an administrator can select up to 3 Scrum boards on the Boards Configuration page.
Only data within the selected tracking scope is synchronized:
- A sprint is tracked only when its origin board is selected
- A work item is tracked only when it belongs to the space associated with the selected board
- Boards that are not selected are not tracked
- Sprint Reporting fields, JQL data, dashboards, and audit logs include only data from the selected tracking scope
- The Orphan Sprints feature is not available
Changes to tracked sprints and work item movement between sprints are detected by scheduled background synchronization and may take up to 5 minutes to appear.
Recommended Board Configuration
For reliable tracking in the Free Edition:
- Select all Scrum boards belonging to the space you want to track
- Make sure every selected board contains only work items from its associated space
The Free Edition works correctly when all work items displayed by a selected board belong to the same space as that board and all Scrum boards from that space are selected.
Cross-Space Boards
A Jira board can use a filter that displays work items from multiple spaces. In the Free Edition, selecting such a board does not extend tracking to every space represented by its filter.
Sprint Organizer tracks work items only from the space associated with the selected board. Work items from other spaces displayed on that board are outside the Free Edition tracking scope.
For this reason, boards that combine work items from multiple spaces may produce incomplete Sprint Reporting fields, dashboards, and sprint history in the Free Edition.
Example
Suppose a Scrum board is associated with Space A, but its filter displays work items from both Space A and Space B.
With the Free Edition:
- Sprints originating from the selected board can be tracked
- Work items from Space A can be tracked
- Work items from Space B are not tracked through that board
To avoid incomplete data, configure the board to contain only work items from Space A.
Update Times
An Active License enables event-driven processing for supported sprint changes and work item movement. The Free Edition detects these changes during background synchronization.
Sprint Changes
With an Active License, Jira events are used to process supported changes to existing sprints immediately. This includes changes to:
- Sprint name
- Sprint goal
- Sprint state
- Sprint start date
- Sprint end date
- Sprint completion
With the Free Edition, these changes are detected through background synchronization and may take up to 5 minutes to appear.
Work Items Moved Between Sprints
When an existing work item is moved between sprints, Sprint Organizer updates both its current sprint information and its sprint history.
With an Active License, the movement is processed immediately after the corresponding Jira event is received. With the Free Edition, it is detected and processed within 5 minutes.
This can update fields such as Sprint Name, Sprint State, Closed Sprints, and All Sprints, where applicable.
New Work Items Created in a Sprint
New work items created directly inside a sprint are processed through background synchronization in both editions. Their Sprint Reporting fields may take up to 5 minutes to be populated.
Board Changes
Board name changes and board deletions are processed through background synchronization in both editions. These changes may take up to 5 minutes to be reflected in Sprint Organizer and related Sprint Reporting fields.
Sprint Audit Logs
Sprint Audit Logs are event-driven in both editions. Supported Jira sprint events are processed immediately and do not wait for scheduled synchronization.
Audit logs can record events such as:
- Sprint creation and deletion
- Sprint name and goal changes
- Sprint state changes
- Start and end date changes
- Sprint completion
- Sprint deletion
Where Jira provides the necessary information, entries can also include the user who performed the change, previous and new values, and the event date and time.
Because all updates are asynchronous, there may be a short period during which Sprint Reporting fields still contain their previous values.
For the complete update schedule, see Field Updates.
Boards Configuration
The Boards Configuration page is available only in the Free Edition. It allows administrators to select and manage the boards included in tracking.
Administrators can:
- View the Scrum boards available in Jira
- Search and filter the board list
- Select up to 3 boards for tracking
- Remove previously selected boards
- Review how many boards are selected and how many are allowed
After the configuration is saved, Sprint Organizer begins synchronizing data for the selected boards. Depending on the number of boards and sprints, this may take several minutes. A progress dialog shows the current step, operation, and overall progress.
Do not close or refresh the browser tab while the configuration is being saved.
Removing a selected board permanently deletes tracked data associated with it, including sprint history, audit log entries, and related custom field and JQL values. Adding the board again later starts new tracking and does not restore the previously deleted data.
When the app has an Active License:
- All accessible Scrum boards are tracked automatically
- Manual board selection is not required
- The Free Edition limit of 3 selected boards does not apply
See Boards Configuration for selection, saving, and board removal details.
Orphan Sprints
The Orphan Sprints page is available only with an Active License. It is not available in the Free Edition.
A sprint is considered orphaned when:
- Its origin board no longer exists, and
- The sprint is not available through any other board because none of its work items makes it accessible from another board
Orphan sprints can remain in Jira after their original board or the space containing that board has been deleted.
With an Active License, administrators can use the page to:
- Find and filter orphan sprints
- Review their sprint details, work items, logs, and available reports
- Assign one or more orphan sprints to an existing board
- Permanently delete orphan sprints that are no longer needed
When assigning an active sprint to a board in a company-managed space, parallel sprints must be enabled for that board.
Names of deleted boards and spaces are hidden by default. They can be displayed only when the corresponding override is enabled in Permissions and Sprint Organizer retained the names before the resources were deleted.
The dedicated Orphan Sprints documentation contains the complete description of filters, detection limitations, board assignment, and permanent deletion.
Notes
- An Active License tracks all accessible Scrum boards automatically
- The Free Edition tracks up to 3 selected Scrum boards
- In the Free Edition, tracked sprints must originate from selected boards
- In the Free Edition, tracked work items must belong to the space associated with the selected board
- For complete Free Edition tracking, select all Scrum boards from the space and avoid cross-space board filters
- Orphan Sprints is available only with an Active License
- Jira permissions continue to apply in both editions