workflow says "no incoming transitions to status" when there are (false warning)

[Greg Sarcona]

I have a workflow where recently a warning appears that there are no incoming transitions to a status.  Looking at the workflow diagram, there is a clear path to the status being highlighted.  I've walked test issues through the workflow and have no problems.  The warning is apparently a false alarm.

This warning is preventing us from migrating the workflow from cloud to server installs.

I've disconnected/re-connected the transitions; explored their conditions, validators, and post-functions; added parallel transitions; and the warning remains!

[Greg Sarcona · Accepted solution]

What happened was, during migration, the JSU (jira Suite utilities) rewrote some of the transitions to have post-functions in an inaccurate way.  I got an error message "Could not load FunctionProvider class" when trying to make the state change, where there was a post-function to clear the Resolution field.  I had to edit every transition in every workflow where this error occurred (yes, that meant testing every transition in our workflows schemes!) to rewrite the post-function.  It looks like the post-function code should work, but when I re-wrote it, it was the simple, clear form. (second picture).

Here is the error and its cause:

Here is the corrected form:

This may not be your specific case.  But if you get prevented from state transitions, look into the conditions and post-functions, and compare what you see to transitions which do work. 

CSI: Jira is fun!

:)

[Earl McCutcheon]

Hi Greg,

Thanks for reaching out to the community, but to look into this one we will need to take a look at the erring workflow directly and get some details from the logs.

To get the additional details from you I have created a support request on your behalf that can be viewed at the following link:

• https://getsupport.atlassian.com/servicedesk/customer/portal/42/PSCLOUD-23633

Please log into the Support Portal and provide a link to the affected workflow so we can investigate further.

Regards,
Earl

[Tracey_Mora]

I'm currently experiencing the same issue (a bug perhaps?) and would love to know how this got resolved. 

[Scrum Development]

Same here... I noticed that in my case, the error started when I changed the statuses and unchecked the option Allow ALL Inputs... I guess something clears EVERYTHING and let the status in an unstable condition?

It temporarily gets fixed when I create a new transition from a different status and then I drag/drop the connectors... but after a few more changes, it comes back...