Overview | Sprint Organizer Documentation

Overview documentation.

Overview

Sprint Organizer extends Jira with additional sprint reporting fields that can be used in JQL, dashboards, filters, automations, and reports.

While Jira's native Sprint field provides only limited querying capabilities, Sprint Organizer synchronizes additional sprint metadata to issue-level custom fields, making it possible to search issues using sprint names, sprint states, goals, dates, boards, and historical sprint participation.

These fields are updated automatically during background synchronization and are available throughout Jira anywhere custom fields can be used.

Sprint Reporting fields support exact value matching.

• Advanced Search (JQL) provides autocomplete suggestions for supported text fields such as Sprint Name, Sprint Goal, Sprint Board, Closed Sprints, and All Sprints.
• Basic Search supports only exact value matching for text-based Sprint Reporting fields and does not provide autocomplete suggestions due to current Jira limitations for Forge custom fields.
• Text-based Sprint Reporting fields support both the = and IN operators.
• Date fields fully support both Advanced Search and Basic Search.
  {.img-center .img-large}

Search Capabilities

All date fields support both Advanced Search (JQL) and Basic Search.

Examples of supported JQL expressions include:

"Sprint CompleteDate" < endOfMonth()

Basic Search supports the standard Jira date operators, including:

• Between
• In the last
• More than
• In the range

{.img-center .img-medium}

All text-based Sprint Reporting fields support both the = and IN operators.

The IN operator can be used to match multiple values in a single query.

Example

"Closed Sprints" IN ("GW Sprint 1", "ILLUMINA Sprint 1")

Available Fields

Sprint Organizer provides the following custom fields.

Sprint Name

Contains the name of the issue's current Active or Future sprint.

Typical use cases:

• find issues currently assigned to a specific sprint,
• create sprint-specific dashboards,
• filter issues by sprint name.

Example

"Sprint Name" = "Sprint 42"

The field also supports searching by sprint ID.

Example

"Sprint Name" = 42

Search suggestions:

{.img-center .img-medium}

Sprint State

Stores the current state of the issue's active or future sprint.

Supported values:

• Active
• Future

Closed sprints are tracked separately using the Closed Sprints field.

Example

"Sprint State" = Active

Sprint Goal

Contains the goal of the current Active or Future sprint.

Useful for reporting or identifying issues belonging to sprints with specific planning objectives.

Example

"Sprint Goal" = "Release 2.0"

Advanced Search provides autocomplete suggestions for available sprint goals.

Basic Search requires entering the exact goal value.

Sprint Start Date

Stores the scheduled start date of the current Active or Future sprint.

Typical use cases:

• reporting,
• automation,
• date-based filtering.

Example

"Sprint StartDate" >= "2026-01-01"

Sprint End Date

Stores the planned end date of the current Active or Future sprint.

This field can be used to locate issues belonging to sprints ending within a selected period.

Example

"Sprint EndDate" <= "2026-12-31"

Sprint Complete Date

Contains the actual completion date of a sprint after it has been closed.

Useful for historical reporting and sprint analytics.

Example

"Sprint CompleteDate" >= "2026-07-01"

Sprint Board

Stores the name of the Scrum board that originally owns the sprint.

This makes it easy to identify issues belonging to sprints from a specific board.

Example

"Sprint Board" = "Backend Scrum"

The field also supports searching by board ID.

Example

"Sprint Board" = 15

Advanced Search provides autocomplete suggestions for all available Scrum boards.

Basic Search supports exact matching by board name or board ID.

Closed Sprints

Contains all completed sprints the issue has previously belonged to.

Unlike Jira's native Sprint field, this field preserves sprint history after an issue moves into a new sprint.

A maximum of 40 closed sprint entries is stored per issue.

Typical use cases:

• identify issues completed in a particular sprint,
• review previous sprint participation,
• build release reports.

Example

"Closed Sprints" = "Sprint 25"

The field also supports searching by sprint ID.

Example

"Closed Sprints" = 25

Advanced Search provides autocomplete suggestions for all known sprint names.

Basic Search supports exact matching by sprint name or sprint ID.

All Sprints

Contains every sprint the issue has ever been assigned to, including:

• completed sprints,
• the current Active sprint,
• Future sprints.

This field provides the complete sprint history of an issue.

A maximum of 40 sprint history entries is stored per issue.

Typical use cases:

• trace issue movement between sprints,
• reporting,
• historical analysis,
• advanced JQL filters.

Example

"All Sprints" = "Sprint 12"

The field also supports searching by sprint ID.

Example

"All Sprints" = 12

Advanced Search provides autocomplete suggestions for all known sprint names.

Basic Search supports exact matching by sprint name or sprint ID.

Synchronization

Sprint Reporting fields are synchronized automatically in the background.

Synchronization updates include:

• sprint name changes,
• sprint goal changes,
• sprint state changes,
• sprint board changes,
• sprint start date changes,
• sprint end date changes,
• sprint completion,
• issue movement between sprints.

Because synchronization is asynchronous, updates are not reflected immediately after changes are made in Jira.

Search results and field values are refreshed after the next synchronization cycle.

Synchronization frequency depends on the license status:

See Asynchronous Synchronization for more information.

Common Use Cases

Sprint Reporting fields enable advanced queries that are difficult or impossible using Jira's native Sprint field.

Examples include:

• Find issues currently planned for a sprint.
• Find all issues completed in a specific sprint.
• Find issues that have ever belonged to a sprint.
• Find issues assigned to sprints from a specific Scrum board.
• Create dashboards grouped by sprint state.
• Build automations based on sprint start, end, or completion dates.
• Generate reports using complete sprint history.
• Search issues by sprint goal.
• Filter issues using sprint IDs instead of sprint names.

Permissions

Sprint Reporting fields fully respect Jira's permission model.

Users can search and view only the issues they are already authorized to access.

Sprint Organizer never exposes sprint information for inaccessible issues, projects, boards, or spaces.

Limitations

The following limitations apply to Sprint Reporting fields:

• Text-based Sprint Reporting fields support exact value matching only.
• The ~ (contains) operator is not supported.
• Autocomplete suggestions are available only in Advanced Search (JQL).
• Due to current Jira limitations for Forge custom fields, Basic Search does not provide autocomplete suggestions for text-based Sprint Reporting fields.
• Synchronization is asynchronous, so recently changed sprint information may not be searchable until the next synchronization cycle.
• A maximum of 40 entries is stored per issue in both the Closed Sprints and All Sprints fields.

Related Pages

• Asynchronous Synchronization
• Dashboard
• Sprints
• Sprint Audit Log
• Deleted Sprint Tracking
• Permissions