Sprint Association Removed After Workflow Update – Assistance Required

[Jay Sharma]

We recently updated our project workflow by simplifying and modifying the existing statuses. After publishing the updated workflow, we noticed unexpected behavior across the board.

A large set of tickets were automatically transitioned to different statuses. More importantly, tickets that were previously part of closed sprints now show the Sprint field as “None.” We are no longer able to see those tickets associated with their original sprints in the backlog or in reports.

These tickets were already part of completed sprints, and the sprint association now appears to have been removed following the workflow update.

We would like to understand:

• Why the sprint field was cleared after the workflow change.

• Whether it is possible to restore the original sprint associations.

• If there is any safe recovery or rollback option available.

This has impacted our sprint reporting and historical data, so your guidance on the appropriate recovery steps would be greatly appreciated.

Please let us know if any additional details are required from our end.

[Arkadiusz Wroblewski]

Hello and Welcome @Jay Sharma 

A workflow update by itself doesn’t normally wipe Sprint values. Changing statuses can move issues around, but it shouldn’t turn Sprint into “None”. So something else likely changed at the same time.

Here’s where I’d look first:

1) Board filter / board scope changed
Sprint reporting is tied to what the board considers “in scope”. If the board’s JQL was tightened (or quick filters/board settings changed), issues from old sprints can suddenly “disappear” from backlog and reports.
Check: Board → Board settings → the board filter (JQL). Compare with what it used to be.

2) Automation or bulk update cleared the Sprint field
If the issue view itself now shows Sprint = None, that usually means something edited that field (automation, bulk edit, CSV import, script).
Check the project Automation audit log around the time you published the workflow and when the mass transitions happened.

3) Issues were moved out of the board’s project/issue type scope
If anything moved issues to a different project, changed issue type, or otherwise dropped them out of the board filter, they won’t show in sprint views.

On recovery:

If it’s a board filter/scope issue, fixing the board scope brings everything back immediately.

If Sprint values were truly cleared, there’s no “magic restore” button. You’re looking at rebuilding it (CSV/script) or involving Atlassian support if you need confirmation from their side.

One quick check to narrow this down:
When you open one affected issue directly, does the Sprint field literally show None, or do you still see a sprint but it just doesn’t show up in backlog/reports?