When sprint started all related story & subtask status changed.

[jyoti.suryan]

Hi,

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

• 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

[Marc -Devoteam-]

Hi @jyoti.suryan 

Welcome to the community.

What do you mean by status changed, to another status or the naming.

The 1st should be visible in work item history.

The 2nd, then an admin changed status names in a workflow and has not have the knowledge that this impact is global.

Any workflow using the status that was renamed is impact by such a change.

So as it seems, it's probably option 2, reach out to your Jira admin,

[Karan Sachdev]

Hey @jyoti.suryan

Welcome to Atlassian Community!

As rightly pointed by @Marc -Devoteam- , statuses are global entities in Jira. So if an admin changed a status name in one of the workflows, the updated name will be reflected in all the associated workflows.

However, this change is captured in the site level audit logs. You may raise a ticket with Atlassian Support so the team can further look into this.

Thanks!

[jyoti.suryan]

Thank you @Karan Sachdev  for clarity.