Transition failed

[kristyna.ludwigova]

Hello,

when I tried to move task to different state in my workflow, I got error saying "Transition failed, Internal server error". It is happening only for few states, not all.  I've checked transition settings and post function and didn't find anything wrong.

Can you advise me what can I do or look for?

Thanks!

[Nic Brough -Adaptavist- · Accepted solution]

Welcome to the Atlassian Community!

On Cloud, we can't get to the logs to see what the problem is, but in this case, I would guess that it is the first post-function failing, and it's probably permissions or settings.

Just to confirm, I assume you have "allow unassigned issues" enabled, so that you can leave the assignee blank.  If it was disabled, the post-function can't set the assignee to unassigned, even though the option would be offered when configuring the post-function.

The other possibility is that the current user, the one using the transition, does not have the permission to assign the issue to anyone.

[kristyna.ludwigova]

Hi, thanks for advice. I have "allow unassigned issues" enabled and since I am admin I guess it is not caused by permission. I am not sure how to get logs. Is there anything else what can I do?

[Walter Buggenhout]

Hi @kristyna.ludwigova ,

In cloud you can't access the logs unfortunately. Being an admin does not automatically grant you assignable user permission nor assign issue permission in a project. Do verify if everything is ok in that aspect.

If that does not help and you seem to be on a premium plan, do reach out to Atlassian support. If there is something wrong with your site, they should be able to diagnose from the logs. 

[kristyna.ludwigova]

Thanks for your help!

I have permissions for this project set like this:

Seems ok to me. Anyway when I deleted first post function rule, it is working but that rule was helpful and team wants it back. So do you think the permission on screenshot are wrong?

[Nic Brough -Adaptavist-]

Ok, so the permissions all look fine, and "any logged in user" can assign issues, so it's not that.

The only thing left in my theory is to check that the user you are trying to assign the issue to is in the role of "member" in the project?

[kristyna.ludwigova]

Yes, members roles are correct. I actually added the post function again but differently and it is working. So thank you for all your advices. It has been really helpful! It is good to know that there is such great community ready to help!

[Dan H]

Just in case anyone else comes to this forum looking for answers to the illusive:
Internal server error

For us, I eventually managed to spot the issue was caused after deleting a Custom Field, and how badly Jira's Post-Functions handles this:

So I simply just removed the broken post-function (step 3) and problem solved!

[Chris.Parkes]

This is very similar to the problem I faced, solved the same way. Look very closely at the post-functions after updating workflows.

[Walter Buggenhout]

Hi @kristyna.ludwigova,

The only thing on this list of post functions that may ring a bell is the first one: do make sure that all users transitioning issues in your project also have the assign issues permission. Apart from that, there is nothing apparently suspicious in your configuration here.

Hope this helps! 

[Binod Bihari Das]

Withdrawal and processing Transition next day failed what is issue 

[Bill Sheboy]

Hi @Binod Bihari Das -- Welcome to the Atlassian Community!

Please create a new question, including details of your workflow and a description of what you observe that is unexpected.

Otherwise only the people following this old thread will see what you posted.

Kind regards,
Bill

[Sümeye Beki]

Hi @kristyna.ludwigova 

I think you should look for the logs. You can find detailed information what blocks the transition. For example, if you made the assignee field "required" in the field configuration scheme, or there is condition on the destination status checks for the assignee null condition, this may be a problem. But to be sure, you should check the logs to see what workflow is trying to do.