Deleted Sprint Tracking | Sprint Organizer Documentation
Deleted Sprint Tracking documentation.
Deleted Sprint Tracking allows administrators to retain visibility into sprints that have been removed from Jira.
By default, deleted sprints are no longer available in Jira, making it difficult to investigate historical planning activities or understand why sprint-related data has disappeared. Sprint Organizer preserves essential metadata for deleted sprints, allowing administrators to review their history even after the sprint no longer exists in Jira.
This feature improves traceability, supports auditing, and helps teams investigate unexpected sprint removals.
How Deleted Sprints Are Detected
Sprint Organizer detects sprint deletions using Jira events.
When a sprint is deleted in Jira, Jira sends a corresponding deletion event to Sprint Organizer. The application processes this event and marks the previously synchronized sprint as Deleted instead of removing its stored metadata.
This allows the deleted sprint and its previously synchronized information to remain available for historical reporting and auditing.
Information Preserved
When a sprint is marked as deleted, Sprint Organizer retains the sprint metadata collected before deletion.
Depending on the available information, this may include:
- Sprint Name
- Sprint State
- Sprint Goal
- Board
- Space
- Start Date
- End Date
- Complete Date
- Creation Date
The original Jira sprint is not preserved. Sprint Organizer stores only the synchronized metadata required for historical analysis.
Viewing Deleted Sprints
Deleted sprints are available throughout Sprint Organizer.
They can be viewed by:
- Filtering the Sprints page by the Deleted state,
- Reviewing sprint deletion events in the Sprint Audit Log,
- Searching historical sprint participation using the All Sprints Sprint Reporting field.
Deleted sprints are clearly identified to distinguish them from sprints that still exist in Jira.
Data Retention
Deleted sprint information remains available until it is removed according to Sprint Organizer's internal data retention policy.
Deletion tracking begins only after Sprint Organizer has been installed and the sprint has been synchronized by the application.
Sprints deleted before Sprint Organizer was installed or before they were synchronized cannot be tracked because no historical metadata is available.
Sprint Organizer tracks up to 500 deleted sprints per project.
When this limit is reached, older deleted sprint records may be removed as newer deleted sprints are detected.
Permissions
Deleted sprint information follows Jira's permission model.
By default, users can only access information associated with projects and boards they are authorized to view. Project and board names that are unavailable due to Jira permissions are not displayed.
Administrators can optionally enable permission overrides to display stored Project Names and Board Names even when the corresponding project or board is private, deleted, or inaccessible to the current user.
Permission overrides are configured separately for:
- Jira administration pages – controls the visibility of stored project and board names on Sprint Organizer administration pages.
- Project pages – controls the visibility of stored board names within individual Jira projects.
Permission overrides affect only the visibility of stored names. They do not grant access to the underlying Jira project, board, sprint, or issue.
Because these settings may expose names that users would not normally be able to see in Jira, they should only be enabled when appropriate for users who can access the corresponding Sprint Organizer pages.
To learn more, see Permissions Settings.
Limitations
Deleted Sprint Tracking has several important limitations:
- Only sprints previously synchronized by Sprint Organizer can be tracked after deletion.
- Sprints deleted before installation or before initial synchronization cannot be tracked.
- Detection depends on Jira sprint deletion events being delivered to Sprint Organizer.
- Sprint Organizer preserves synchronized metadata, not the original Jira sprint.
- Availability of deleted sprint information depends on Jira permissions.
- A maximum of 500 deleted sprints per project is tracked.