FAQ | Sprint Organizer Documentation

FAQ documentation.

This page answers frequently asked questions about Sprint Organizer for Jira, including Sprint Reporting, synchronization, permissions, licensing, deleted sprints, orphan sprints, and administration.

General

What is Sprint Organizer for Jira?

Sprint Organizer is a Jira Cloud app that provides centralized sprint visibility, reporting, auditing, and administration across multiple Scrum boards.

It extends Jira with features such as:

Which Jira project types are supported?

Sprint Organizer works with Jira Software projects using Scrum boards and sprints, including:

Does Sprint Organizer replace Jira's native sprint functionality?

No.

Sprint Organizer works with native Jira sprints and adds additional visibility, reporting, historical tracking, and administration capabilities.

Sprint creation, sprint states, work items, boards, and permissions remain part of Jira.

What is the difference between Global Administration and Space Pages?

Global Administration provides a Jira-wide view of accessible sprint information across multiple spaces and Scrum boards.

Space Pages limit sprint information to boards associated with the current Jira space.

Both use the same Jira permission model.

Sprint Reporting & JQL

What are Sprint Reporting fields?

Sprint Reporting fields are Jira custom fields created by Sprint Organizer that expose additional sprint information at the work item level.

Available fields include:

These fields can be used in JQL, filters, dashboards, reports, and automations.

See Sprint Reporting & JQL for details.

Why should I use Sprint Reporting fields instead of Jira's native Sprint field?

Jira's native Sprint field provides limited access to sprint metadata in JQL.

Sprint Reporting fields make additional information available for searching, including sprint state, goal, dates, board, and historical sprint participation.

For example:

"Sprint State" = Active

or:

"Sprint End Date" < now()

Can I search by sprint name or ID?

Yes.

Sprint Reporting fields such as Sprint Name, Closed Sprints, and All Sprints support searching by sprint ID.

When storing Sprint Names is enabled in Sprint Organizer's Permissions settings, they can also be searched by name.

Examples:

"Sprint Name" = "Sprint 42"

"Sprint Name" = 42

Can I search for multiple sprint values?

Yes.

Text-based Sprint Reporting fields support the IN operator.

Example:

"Closed Sprints" IN ("Sprint 10", "Sprint 11", "Sprint 12")

Does Sprint Reporting support partial text searches?

No.

Text-based Sprint Reporting fields currently support exact value matching.

The ~ (contains) operator is not supported.

Why don't I see autocomplete suggestions in Basic Search?

Due to current Jira limitations for Forge custom fields, autocomplete suggestions for text-based Sprint Reporting fields are available only in Advanced Search (JQL).

Basic Search supports exact value matching but does not provide autocomplete suggestions for these fields.

Can Sprint Reporting fields be used in Jira dashboards?

Yes.

Sprint Reporting fields are standard Jira custom fields and can be used with Jira filters and many standard dashboard gadgets, including:

See Dashboards & Filters for examples.

How much sprint history is stored in Closed Sprints and All Sprints?

Sprint Organizer stores a maximum of 40 entries per work item in:

Synchronization

Are Sprint Reporting fields updated automatically?

Yes.

Sprint Organizer automatically synchronizes sprint information in the background.

No manual synchronization is normally required.

Why are my Sprint Reporting fields not updated immediately?

Sprint Organizer uses both Jira events and scheduled background synchronization.

With an Active License, supported changes to existing sprints and movements of existing work items between sprints are processed immediately after the corresponding Jira event is received.

Some operations are processed within 5 minutes, including:

With the Free Edition, sprint changes and work item movements may also take up to 5 minutes to appear.

See Field Updates for the complete update schedule.

I created a new work item in a sprint. Why are its Sprint Reporting fields empty?

New work items created directly inside a sprint are processed through background synchronization.

Their Sprint Reporting fields may take up to 5 minutes to be populated in both the Free Edition and with an Active License.

Do I need to keep Sprint Organizer open while synchronization is running?

No.

Synchronization and background updates continue automatically. Sprint Organizer does not need to remain open.

Deleted Sprints

Can Sprint Organizer show deleted sprints?

Yes.

Sprint Organizer tracks deleted sprints and preserves synchronized sprint metadata for historical analysis and auditing.

Deleted sprints can be found on the Sprints page by filtering for the Deleted state.

Can Sprint Organizer show sprints that were deleted before the app was installed?

No.

Deleted Sprint Tracking begins after Sprint Organizer is installed and the sprint has been synchronized.

If a sprint was deleted before installation or before Sprint Organizer synchronized it, the app does not have the historical metadata required to track it.

Can a deleted sprint be restored?

Yes.

Sprint Organizer can create a new Jira sprint based on metadata preserved for a deleted sprint.

The restored sprint is a new Jira sprint and receives a new sprint ID. The original sprint and its original ID cannot be recreated.

See Restore Sprints for details.

Are work items automatically restored when I restore a sprint?

No.

After creating the new sprint, Sprint Organizer can display work items previously detected as belonging to the deleted sprint.

You can review and select which work items should be added to the restored sprint.

Work items associated with the original sprint within the last 1 hour are selected by default, but the selection can be changed before adding them.

How many deleted sprints are retained?

Sprint Organizer tracks up to 500 deleted sprints per project.

When this limit is reached, older deleted sprint records may be removed as new deleted sprints are detected.

Orphan Sprints

What is an orphan sprint?

An orphan sprint is a sprint whose original Scrum board no longer exists and which is not available through another existing board.

Such sprints may remain in Jira even after their original board has been deleted.

Sprint Organizer provides a dedicated Orphan Sprints page to help administrators locate and manage them.

Can I assign an orphan sprint to another board?

Yes.

Select one or more orphan sprints and use Assign Board to associate them with an existing Scrum board.

When assigning an Active sprint to a board in a Company-managed space, parallel sprints must be enabled for that board.

Can I delete an orphan sprint?

Yes.

Orphan sprints can be permanently deleted from the Orphan Sprints page.

Deleting a sprint is permanent. Review its work items and available historical information before confirming the operation.

Why is the original board or space name missing for an orphan sprint?

Sprint Organizer can display historical Board or Space Names only if those names were previously known to the app.

If the board or space was deleted before Sprint Organizer was installed, its name may not be available.

Permission settings may also affect whether stored names are displayed.

Are Orphan Sprints available in the Free Edition?

No.

The Orphan Sprints feature is available only with an Active License.

Audit Log

What changes does Sprint Audit Log track?

Sprint Organizer records the following sprint lifecycle events:

Depending on the event, additional details may include previous and new values, dates, sprint goals, board information, and information about the user who performed the action.

How many Audit Log events are stored?

Sprint Organizer stores the most recent 500 sprint events in an Audit Log.

Older events are removed as new events are recorded.

Can I see sprint changes that happened before Sprint Organizer was installed?

No.

Sprint Organizer cannot reconstruct sprint events that occurred before the app was installed.

Why is an expected event missing from the Audit Log?

Possible reasons include:

Sprint Audit Log events are processed from Jira events immediately in both editions.

Permissions & Privacy

Does Sprint Organizer respect Jira permissions?

Yes.

Sprint Organizer uses Jira's existing permission model and does not create a separate access control system.

Users can access only Jira resources they are authorized to view unless an administrator explicitly enables one of Sprint Organizer's permission overrides for stored resource names.

Do permission overrides give users access to private Jira resources?

No.

Permission overrides affect only the visibility of selected stored names.

They do not grant access to the underlying:

Why are Sprint Names or Board Names missing from Sprint Reporting fields?

By default, Sprint Organizer does not store Sprint Names or Board Names in Sprint Reporting custom fields.

This prevents names of private, inaccessible, or deleted resources from being exposed through Jira custom fields.

Administrators can optionally enable storing these names in Permissions Settings.

See Permissions for details.

What happens when storing Sprint Names or Board Names is enabled?

Sprint and/or Board Names can become available through Sprint Reporting fields in:

Because Jira text-based custom fields cannot dynamically hide individual values based on the permissions of the user viewing a work item, stored names may include resources that the user would not normally be able to access directly in Jira.

Enabling this setting does not grant access to those resources.

Why do different users see different sprint information?

Sprint Organizer follows Jira permissions.

If two users have different access to spaces, boards, or work items, the sprint information available to them may also differ.

Licensing

Is there a Free Edition?

Yes.

Sprint Organizer can be used with an Active License or as the Free Edition.

What is the main limitation of the Free Edition?

The Free Edition tracks up to 3 manually selected Scrum boards.

With an Active License, all accessible Scrum boards are tracked automatically.

How do I select boards in the Free Edition?

Jira administrators can select boards from the Boards Configuration page.

For reliable tracking:

See Boards Configuration for details.

What happens if I remove a tracked board in the Free Edition?

Removing a board from Boards Configuration permanently deletes Sprint Organizer tracking data associated with that board, including:

Adding the board again later starts tracking from that point forward. Previously deleted tracking data is not restored.

Does the Free Edition update data more slowly?

For some operations, yes.

With an Active License, supported sprint changes and movements of existing work items between sprints are processed immediately after Jira events are received.

In the Free Edition, these changes are processed through background synchronization and may take up to 5 minutes.

Some operations, including newly created work items and board changes, may take up to 5 minutes in both editions.

Sprint Audit Log events are processed immediately in both editions.

Are all features available in the Free Edition?

No.

The main documented differences are:

See Licensing for the complete comparison.

Administration

Can Sprint Organizer manage sprints from multiple boards?

Yes.

Global Administration provides a centralized view of accessible sprints across multiple Jira spaces and Scrum boards.

The Sprints page can be used to search, filter, and inspect sprint information without opening each Jira board individually.

Can I filter sprints by state?

Yes.

Sprint lists support the following states:

Additional filters are available for spaces, boards, dates, and text search.

Can I filter sprints by dates?

Yes.

Sprint lists support date-range filtering using:

Why can't I see a sprint that exists in Jira?

Common reasons include:

Check your Jira permissions, board configuration, and synchronization status.

Troubleshooting

What should I check before contacting support?

Before contacting support:

  1. Verify your Jira permissions.
  2. Check whether the affected board is tracked by Sprint Organizer.
  3. Allow background synchronization to complete.
  4. Review active filters.
  5. Check the Sprint Audit Log for recent changes.
  6. Review the Troubleshooting Guide.

If the issue persists, collect screenshots, reproduction steps, and the approximate timestamp of the issue before contacting support.

Related Pages