Failing to transition because the transition found by algorithm `Stop Progress` is no longer available for current step `In Progress` (3) Please contact Exalate Support
Available transitions: `Resolve Issue`, `Close Issue`, `to Review`

1 answer

1.  

   2

   1

   0

   • Juan Grases
   • May 05, 2020

   We have seen that error when the issue type of the issue has been changed using the Jira Cloud REST API between 2 issue types with different workflows. For some reason, Jira Allows to perform the change but then there are some inconsistencies when dealing with the statuses of the issue. 

   Exalate uses the Jira cloud rest API so it's also affected by this, this error might be happening because in your incoming processor you are trying to set the issue type

   issue.type = replica.type
   //or
   issue.typeName = replica.typeName
   //or similars

   To avoid this situation I would recommend only changing the types if you know they share the same workflow, the other approach is only setting the type on the first sync (when issue is created by exalate)

   
   

   if(firstSync){
     //only set the type in the firstSync block
     issue.typeName = replica.typeName
   }

   •  Comment

   CommentAdd your comment...