The selft reflecting (Self Transition) to same status does not work in Cloud.

[Santhosh R Bhat]

Hello All,

I m using Jira Cloud.

I have 3 status in my workflow. New, In Progress, Done.

When a issue status is changed to "Done" a "Resolution" screen is shown where user has to set the resolution drop down field value for the issue. 

Suppose he sets a wrong resolution then I would like to add a transition from "Done" to "Done" so that the resolution screen appears again and user gets a chance to correct the resolution rather than going back to "In Progress" and then transition it back to "Done".

In the work flow I have set this resolution and i have set the screen name properly. 

But in issue view screen or on the board, it is not possible to change the status from "Done" to Done.

Anything else I have to setup for this to work. 

Pl. help.

Thanks

[Evgenii · Accepted solution]

Hi, @Santhosh R Bhat 

It's not in Transitions list. It's in Actions list.

[Santhosh R Bhat]

Hello @Evgenii ,

Thank you very much for your quick and to the point answer.

This helped a lot.

I m not able to make this change in the sprint board. Can you pl. help on how to do it.

Thanks again.

Santhosh R. Bhat

[John Funk]

Hi Santosh 

Did you publish the workflow with your changes to include the looping transition on Done? 

If so, are there any Conditions on the transition?

[Santhosh R Bhat]

Hello @John Funk ,

Yes, I have done all those steps. No conditions set.

I was looking in the Transition drop down list. But it is in the "Actions" drop down list now.

My query is resolved by @Evgenii 

Thank you for responding to my query.

Santhosh R. Bhat

[Kasturee]

Hi @Evgenii Thank you for your answer. Do you know why Atlassian has added this to the Actions List and not the Transitions drop down? If I configure the self transition to be visible in the Customer Portal then it displays in the portal with all the other Customer Portal transitions.

[Evgeniy Isaenkov]

Hi, @Kasturee 

Sorry, I don't know, what was the root reason, why Atlassian UI designers decided, that it must be in another place. It's weird solution.