The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

transitions are not exalated from cloud to server

OC
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
March 12, 2020

Hi,

 

I have problems changing the issue status via exalate from cloud to the server.

Transitions are exalated correctly from server to the cloud.

In Cloud / outgoing sync:

replica.status = issue.status

On the Server / Incoming sync e.g.:

if (replica.status.name == "Selected for Development") {
//throw new com.exalate.api.exception.IssueTrackerException(replica.status.name+ " issue stat name: " +issue.status.name)
workflowHelper.transition(issue, "To Do")
}

If I do activate the comment, I get following information:  Selected for Developmentissue stat name:To Do

 

So the if-statement works fine. For testing purposes I gave also admin rights to the proxy user, but still no success.

 

Looking forward for any idea, what might be wrong.

 

Thank you in advance,

 

OC

0 answers

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question