Key Concepts | Sprint Organizer Documentation

Key Concepts documentation.

Sprint Organizer helps teams work with sprint information beyond the
limits of individual Jira boards.

Instead of opening boards one by one to understand what is happening,
you can use Sprint Organizer to find sprints across spaces, search
work items by sprint metadata, build sprint-based reports, review sprint
history, and manage sprints that are difficult to find or no longer have
a board.

This page introduces the main ways Sprint Organizer can be used.

See All Your Sprints in One Place

In Jira, sprint management is usually centered around individual Scrum
boards.

This works well when you are focused on one team, but becomes harder
when you need to answer questions across multiple boards or spaces, such
as:

Which sprints are currently active?
Which sprints are planned next?
Which active sprints are already past their end date?
What happened to a sprint that is no longer visible on its original
board?
Which boards or spaces have recently created, started, completed, or
deleted sprints?

Sprint Organizer provides centralized sprint views so you can search and
filter sprint information without navigating through every Scrum board
separately.

Use:

Global Administration when you need visibility across accessible spaces and boards.
Space Pages when you want to focus on sprint activity within a particular Jira space.

Turn Sprint Information into Searchable Jira Data

One of the main purposes of Sprint Organizer is to make sprint metadata
available for normal Jira reporting.

Sprint Organizer adds Sprint Reporting fields such as:

Sprint Name
Sprint State
Sprint Goal
Sprint Board
Sprint Start Date
Sprint End Date
Sprint Complete Date
Closed Sprints
All Sprints

This means you can search for work items using information that is
difficult or unavailable to query through Jira's native Sprint field.

For example, you can find work items in active sprints:

"Sprint State" = Active

Find unfinished work in active sprints that have already passed their
planned end date:

"Sprint State" = Active AND "Sprint End Date" < now() AND status != Done

Or find work planned in upcoming sprints:

"Sprint State" = Future

Once you create a JQL filter, the same sprint information can be reused
in Jira dashboards, reports, filters, and automations.

→ See: Sprint Reporting &
JQL & Dashboards & Filters

Build Sprint Reports Beyond a Single Board

Sprint Organizer is useful when sprint reporting needs to go beyond
Jira's standard board-based views.

Because Sprint Reporting data is exposed through Jira custom fields, you
can combine sprint information with normal Jira criteria such as:

Status
Assignee
Priority
Space
Work item type
Resolution

For example, a saved filter can identify unfinished work in overdue
active sprints and then be displayed using standard Jira dashboard
gadgets.

Sprint Reporting fields can be used with gadgets such as:

Filter Results
Work Item Statistics
Pie Chart
Two Dimensional Filter Statistics
Filter Counts
Created vs Resolved Chart

This makes it possible to create reporting views around questions that
involve both work item data and sprint data.

→ See: Dashboards & Filters

Understand What Happened to a Sprint

Sometimes the important question is not where a sprint is now, but
what happened to it.

Sprint Organizer's Sprint Audit Log records sprint lifecycle events
including:

Added
Edited
Started
Closed
Deleted

You can use the Audit Log to investigate recent sprint activity and
review changes without relying only on the sprint's current state.

Depending on the event, additional details may include previous and new
values, dates, sprint goals, board information, and other sprint
metadata.

Typical uses include:

Checking when a sprint was started or completed
Reviewing changes to sprint dates or goals
Identifying deleted sprints
Understanding recent sprint activity across a space or Jira
instance

The Global and Space Audit Logs each retain the most recent 500 sprint
events in their respective scope.

→ See: Sprint Audit Log

Keep Sprint History After Deletion

Deleting a sprint in Jira normally removes the original sprint from
normal use.

If Sprint Organizer synchronized the sprint before it was deleted, it
can preserve available metadata about that sprint.

This allows deleted sprints to remain useful for:

Historical analysis
Searching previous sprint participation
Reviewing deletion events
Investigating why a sprint disappeared
Creating a replacement sprint when necessary

Deleted sprints can be found on the Sprints page using the
Deleted state filter.

Sprint Organizer can also use preserved metadata to help create a
replacement sprint through Restore Sprints.

A restored sprint is always a new Jira sprint with a new sprint ID.
Sprint Organizer cannot recreate the original deleted Jira sprint.

→ See: Deleted Sprint
Tracking & Restore Sprints

Find Sprints Left Behind by Deleted Boards

Deleting a Scrum board does not always mean that its sprints disappear
from Jira.

A sprint whose original board no longer exists and which is not
available through another existing board can become an Orphan
Sprint.

These sprints can be difficult to locate and manage through normal Jira
navigation.

Sprint Organizer provides an Orphan Sprints view where
administrators can identify these sprints and decide what to do with
them.

Depending on the situation, an orphan sprint can be:

Assigned to an existing Scrum board, or
Permanently deleted.

Orphan Sprint management is available with an Active License.

→ See: Orphan Sprints

Use Current and Historical Sprint Membership

Sprint Organizer can help answer both:

Where is this work item planned now?
Which sprints has this work item belonged to?

Fields such as Sprint State, Sprint Goal, Sprint Board, and
sprint dates provide information about the relevant Future or Active
sprint.

Historical fields provide a longer view:

Closed Sprints -- closed sprints in which the work item
participated
All Sprints -- sprint history associated with the work item

This is useful when you need to search or report on work based not only
on its current sprint, but also on previous sprint participation.

Both historical fields retain up to 40 sprint entries per work item.

→ See: Fields
Overview

Work Globally or Within a Single Space

Sprint Organizer provides the same core sprint information at two useful
levels.

Global Administration

Use Global Administration when you need to work across multiple
accessible spaces and Scrum boards.

Typical uses include:

Finding sprints across the Jira instance
Comparing sprint activity across spaces
Reviewing global sprint statistics
Investigating sprint changes across boards
Administering orphan sprints

Space Pages

Use Space Pages when your work is focused on one Jira space.

Typical uses include:

Checking Active, Future, Closed, and Deleted sprints for the space
Viewing sprint activity and statistics
Searching the space's sprints
Reviewing the space's Sprint Audit Log
Investigating orphan sprints associated with the space

What you can see in either view continues to depend on your Jira
permissions.

→ See: Global
Administration & Space Pages

Understand What Sprint Organizer Tracks

Sprint Organizer automatically keeps its sprint information synchronized
with Jira, but the amount of data it tracks depends on the license.

Active License

With an Active License, Sprint Organizer automatically tracks all
accessible Scrum boards.

This is designed for teams that want broader sprint visibility without
manually maintaining a list of boards.

Free Edition

With the Free Edition, you choose up to 3 Scrum boards to track.

Only boards within that configured scope are tracked.

This makes the Free Edition suitable for evaluating Sprint Organizer or
using it with a limited set of Scrum boards.

When using the Free Edition, removing a board from Boards
Configuration permanently removes Sprint Organizer tracking data
associated with that board.

→ See: Boards
Configuration & Licensing

Expect Updates to Happen Automatically

You normally do not need to refresh or manually synchronize Sprint
Organizer data.

The app updates information in the background.

With an Active License, supported changes to existing sprints and
movements of existing work items between sprints are processed
immediately after Sprint Organizer receives the relevant Jira event.

Other changes may take up to approximately 5 minutes.

In the Free Edition, more updates rely on scheduled synchronization and
may take up to 5 minutes.

The app does not need to remain open while these updates are processed.

→ See: Field Updates

Visibility Still Follows Jira Permissions

Sprint Organizer is designed to extend Jira reporting without replacing
Jira's permission model.

Users do not gain access to a Jira space, board, sprint, or work item
simply because Sprint Organizer knows that it exists.

This means two users may see different sprint information depending on
what they are allowed to access in Jira.

There is one important distinction: administrators can optionally allow
Sprint Organizer to store and display selected Sprint Names, Board
Names, or Space Names in places where those names would otherwise be
hidden.

These settings expose stored names only. They do not grant access to
the underlying Jira resource.

→ See: Permissions