Hi, a colleague somehow managed to change the Done status of all active and inactive workflows, in one go, to some custom status XYZ.
She can't tell how she did it (it may have happened after adding a new workflow).
I'd like to know if there's any way to reverse this operation and put the Done status back in place instead of XYZ?
Login with a user account with admin privileges.
Press the dot key '.'
Start writing Statuses and click on it.
Find the status name you want and click on Edit to be able to change its name.
Alternatively, on Cloud, you can reach the Statuses page by modifying your company name in the following URL: https://YOUR_COMPANY.atlassian.net/secure/admin/ViewStatuses.jspa
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
BTW, note to JIRA: it is overwhelming that I had to ask a work colleague to create an account and upvote my question just to unlock the 3-points-new-user-limitation in order for me to be able to reply to answers to my own question...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
+1'ed
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Perhaps you could have commented on those answers without any restrictions? Technically, you responded by supplying a different answer to your own question, which is conceptually a little odd.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Maybe. Can't recall if I tried or not. However, being used to add another comment on a Jira ticket and seeing this behavior in many answers I read here gives the feeling it should be ok to add a reply. In any case, "You are not permitted to perform this operation" is a poor poor way to help me understand what to do.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Ignacio Pulgar: You da man!
Eventually the status was indeed renamed from Done to XYZ. The reason why it was hard to identify it was that a new Done status was created. This is just part of the Comedy of Errors that's been going on. I guess I chose the wrong week to be on vacation
Thanks for the advice. You saved me a lot of hassle.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Cool :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks @Ignacio Pulgar, but this is not a name changing issue. This new custom status magically took the place of the built-in "Done" status in all schemes.
For example, looking at the "Closed" status (which has a similar role to our "Done" status) in the default JIRA workflow, it is being linked from all other statuses. The change I'm talking about caused the "Closed" status to be replaced with "XYZ" such that now "XYZ" is linked from all the other statuses.
She said that JIRA asked at some point if to perform an operation in all schemes (or something like that) and this caused the replacement to occur in over 20 schemes (backup copies included).
Phill - I agree with Ignacio Pulgar's answer.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Have you tried looking for the status named "XYZ" in the Statuses view? From there, you can Edit its name back to Done, not mattering whether the wizard screen prompted to your colleague or not.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Oh, and that name change will be automatically reflected on all workflows using said status.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Further to the comment from @Ignacio Pulgar check whether your colleague should have full administration privileges or just project administration to avoid a repeat or similar mistake.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I agree admin privileges should only be granted to people who know what they are doing, but knowledge on how to use JIRA is usually acquired by trial and error, and most companies lack expert users when they started using this tool...
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.