at a clients organisation, certain individuals retain admin permissions due to their position, not qualification.
One such individual apparently renamed the default status 1 (open) to a custom name intended for a single workflow and project.
Little did he know, he thus changed the status in over 100 workflows, used in some 300 projects. service desk exploded with complaints about filters and boards not working anymore.
In the status view, the status and step show correctly as "open". If you edit it though, it shows the custom name. Changing back does not work as it says that "open" already exists.
in workflow diagram view of any of the affected workflows, it shows the new custom name.
in workflow text view it shows the old "open" name.
when editing the step, it show step = open mapped to status = "custom name"
JQL queries for status = "custom name" result in a list of issues with status = open, while JQL queirs for status = Open result in empty results.
I understand there is a conceptual difference between status and steps, but at this point I just want to figure out how to get back to normal without having to change hundreds of workflow schemes manually.
Help us, General Atlassian, you are our only hope.
Learn how to use two new reports for next-gen projects in Jira Cloud: Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events