A user has recently reported that the statuses they are able to transition to within a case do not match the statuses within the workflow. This has been tested within the new workflow and the statuses do match. The workflow is mapped to all issues types within the project. Unsure as to why one view shows the correct transition states and the other shows incorrect, is this something anyone one else has come across or any ideas as to why this may have changed? I have republished the workflow, the view workflow shows the correct workflow in both versions of JIRA Cloud but when pressing on the workflow button to transition 6 states are correct, 2 are incorrect but when you transition to them states they rename themselves correctly into the correct state. We are using a kanabn board and every state is able to transition to all others, I am just unsure as to why it is incorrectly showing within the list.
Additionally - The new states that can be seen in the workflow drop down are not in the Statuses section within JIRA. These have never been added and none of the statuses within that workflow or any of the other workflows have been renamed to the best of my knowledge.
I've added your additional information into the main question - that way, if a user votes for an answer future users don't lose access to your full question :)
In regards to the question, I would first check the workflow for what the transitions' are named within the workflow. What is displayed in the status drop-down differs between the two views:
To check if this is the reason, you'll need to be a Jira Admin and then...
Let us know if this resolves your problem :)
Ste
Afternoon Ste
Thanks for the response, it is really appreciated. First of all I will apologies, you are correct with all of the above, I had initially clicked on the status, but didn't take into account that there was potentially a name on the "All to" transition for each one, which now makes so much more sense. I have changed this so thank you for highlighting the above. One query this does lead me to have however is why the previous statuses with the "all" transition ability seemed to copy that of the name of the status, but the two later ones, one being "UAT" - seemingly renamed "Ready for prod" on the old drop down menu was done like this. The only thing I can think is that this has been renamed prior to me starting and has only just been picked up now. Would changing the name of the transition into the status of an all have any impact on other workflows before I go ahead and change them?
I'll accept the answer and I'm thankful for the response, but has just left me with a few queries which are probably internal rather than JIRA related.
Cheers
Ste
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Great - glad this worked!
It will be a user who has renamed the transition - it's not usual for this to be automated (unless they've imported a workflow from the marketplace).
This won't impact other workflows - it just will change the transition names for all projects which use this workflow, so bear that in mind if another team are using it somewhere else!
Ste
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Additionally - The new states that can be seen in the workflow drop down are not in the Statuses section within JIRA. These have never been added and none of the statuses within that workflow or any of the other workflows have been renamed to the best of my knowledge.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.