When sprint started all related story & subtask status changed.

[jyoti_suryan]

On 3rd February, when the sprint was started, the status of all related stories and subtasks changed automatically.

We are using Jira Premium. We have verified the following:

• No Automation rules are configured.

• I have check all the automation rule side by side nothing found.

• No relevant entries are available in the System Audit Log

• Issue history does not show any user or system account that changed the status

• The workflow was reviewed and there are no pre-functions or post-functions configured

In this scenario:

1. Where can we find details of what triggered these status changes?

2. Why are these changes not captured in issue history or audit logs?

3. How can this behavior be prevented or controlled in the future in Jira

[Trudy Claspill]

Hello @jyoti_suryan 

I don't believe that @Ugnius Aušra is correct. I have never had the experience of Jira independently and automatically changing an issue status just because a Sprint was started.

Can you tell us the type of Space this concerns? Click the ... button next to the Space name in the navigation panel on the left. What are the last two lines in the pop-up? They will be something like:

Software space
Company-managed

Can you provide a screen image showing one of these items that was changed when the Sprint started? Show enough of the item so that we can see its current status and the History showing changes to the item.

Can you share a screen image of the Workflow diagram associated with the types of items that experienced this change? 

What was the status of the item before the sprint was started?

Besides Automation Rules there are other methods that can change the status. Certain third party apps can add functionality that "listens" for changes in the system and executes actions as a result of those changes. There could be an integration with an external system that caused the status to be changed. Regardless, a change of the Status should cause a notation in the History of the item.

[jyoti_suryan]

Software Space company manage

Sprint started corresponding stories & subtask status changed from To Do to Development & unit testing.

[Trudy Claspill]

Thank you for the additional information and images.

Is the first workflow image for the story item type? And the second workflow image for the subtask item type?

I can see from the Board image that the Story is in the Status of "Development and Unit Testing",. And I can see that one of its subtasks is in the Status of "In Progress" while the others are "To Do".

Can you provide images of the History tab of the Story showing all the changes made to it?

And can you tell us on what date and at what time the sprint was started?

[Natalia_Kovalchuk_SaaSJet_]

Hi @jyoti_suryan !

When a sprint starts, Jira may automatically apply internal board logic. If board columns allow only specific statuses, Jira can adjust task and sub-task statuses to match them. Jira can also sync subtask statuses with the parent task at the start of the sprint. These changes can be done by the system and aren't recorded as automation or user actions.

In your case, I would like to recommend that you try Issue History for Jira (Work Item History) app from the SaaSJet team. 

Using this app, you can easily do the following:

• See every status change, including:

  • Timestamp

  • Previous → new value

  • Whether multiple tasks changed at once

• Detect bulk updates across the tasks

• Identify patterns like "all changes happened at sprint start"

Moreover, if a sprint start caused unwanted status changes, Issue History for Jira lets you:

• Select multiple tasks

• Revert their statuses in bulk

• Restore the exact previous state

Learn more here - How to Track and Revert Bulk Changes in Jira

Hope it will be helpful!

[Ugnius Aušra]

Hello @jyoti_suryan 

What you’re seeing is expected system behavior in Jira Software Cloud, not a misconfiguration or hidden automation. When a sprint is started, Jira performs an internal system action that evaluates all issues already assigned to that sprint. As part of this process, Jira may automatically update the status of stories and their subtasks so they align with the workflow columns mapped to an active sprint on the board. This action is triggered directly by the sprint start event itself.