Active workflows status changed when a new status is added to a very new workflow

Natalia Bakos
Contributor
October 21, 2024

Hi,

I think my issue is related to this old one: 

https://community.atlassian.com/t5/Jira-questions/Added-a-Status-and-it-now-shows-up-in-many-workflows-that-it-was/qaq-p/1199124

What happened:

  1. One of the admins created a new workflow
  2. On that new workflow he created a new - in progress - status (in the workflow edit page), called "Approved"
  3. All other active workflows changed one - todo - status (which was called Ready) to this new one.
  4. The changed, active workflow still showed that the last change was 3 months ago by me

 

I managed to reproduce the issue when I wanted to fix the workflow:

  1. I opened the active workflow which I wanted to fix.
  2. Since, it didn't allow to change the Approved status to something else, i thought I create a new status, called Ready and just link all the transitions to this
  3. When I started to type the name REA I pressed tab to autocomplete from the suggested status, but it didn't work as I intended and instead, I created a new status, called REA
  4. When I checked the workflows, I saw that all Approved status got renamed to REA and the status type also changed from "in progress" to "to do"
  5. When I went to the issues->statuses page, there were no Ready status at all. 

Why???

I managed to fix this issue by renaming the REA to Ready, but when someone do anything in a new, inactive workflow, then it will mess up all other workflows. Which is just not logical. I don't even understand the purpose of this bug, really. Especially, when it's not allowing me to remove any statuses from an active workflow and I can just rename the name of them. Or add a new status, which messes with ALL the workflows. 

I don't want to mess with our flows anymore, I'm happy it is back to normal (hopefully), but with the above steps I'm sure you can reproduce the issue.

 

Br,

Natalia

1 answer

0 votes
Marc - Devoteam
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 21, 2024

Hi @Natalia Bakos 

It seems someone cloned a workflow and edited this workflow as it was not assigned and renamed a status in the workflow.

Statuses are global in Jira so renaming a status impacts this status name used in any other workflow in the system

Natalia Bakos
Contributor
October 21, 2024

That's the thing, that not just the name has changed, but the status type, which is not possible to change in the workflow edit view. 

And same happened to me without cloning or renaming anything. 

I managed to change the status by just adding a new status to the workflow and rewiring the transitions to the new status (no renaming). When I done with this rewiring and removed the "old" status which wasn't connected to anywhere, it changed the status in EVERY workflow (not just the ones I worked on).

 

Marc - Devoteam
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 21, 2024

Hi @Natalia Bakos 

Then an admin changed the status name and type, but not do this on a workflow, but in the System -> Issues -> Statuses configuration in the Jira System Settings.

 

Natalia Bakos
Contributor
October 21, 2024

Well, I know who did the changes and he didn't change the name and type in the statuses page. I'm sure it's a bug in Jira.

And when I managed to reproduce the issue, I certainly didn't go to the issues page and modify the name and status of the state there. 

Marc - Devoteam
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 21, 2024

Hi @Natalia Bakos 

What you are mentioning, I tried it on my personal and company instance and I can't reproduce this.

This as I can't even remove a status from an active workflow. This can only be done on a copy of a workflow, not active.

The only thing I can think of there is a mismatch in your Cloud instance backend.

Raise an issue at Atlassian Support, they are the only one to check the backend and explain the issue that happened

Natalia Bakos
Contributor
October 24, 2024

Yeh, I opened a support ticket for it.

Like Marc - Devoteam likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events