Hi,
I think my issue is related to this old one:
What happened:
I managed to reproduce the issue when I wanted to fix the workflow:
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
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
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).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.