I have a Jira system setup that has an external tool that is attempting to use the API to update the workflow status of tickets.
The tool is making API calls like this...
127.0.0.1 1194x23586x1 aratouser [08/Oct/2017:19:54:46 +0000] "PUT /rest/api/2/issue/ARATO-6039 HTTP/1.0" 204 - 1198 "-" "-" "15uksdh"
127.0.0.1 1194x23590x2 aratouser [08/Oct/2017:19:54:46 +0000] "GET /rest/api/2/issue/ARATO-6039/transitions HTTP/1.0" 200 2247 108 "-" "-" "7azw1j"
127.0.0.1 1194x23588x2 aratouser [08/Oct/2017:19:54:47 +0000] "PUT /rest/api/2/issue/ARATO-6039 HTTP/1.0" 204 - 1007 "-" "-" "1ra5odm"
127.0.0.1 1194x23592x2 aratouser [08/Oct/2017:19:54:47 +0000] "GET /rest/api/2/issue/ARATO-6039/transitions HTTP/1.0" 200 2247 86 "-" "-" "p59ee4"
127.0.0.1 1194x23591x2 aratouser [08/Oct/2017:19:54:47 +0000] "POST /rest/api/2/issue/ARATO-6039/transitions HTTP/1.0" 204 - 968 "-" "-" "1swpgx7"
127.0.0.1 1194x23593x2 aratouser [08/Oct/2017:19:54:47 +0000] "POST /rest/api/2/issue/ARATO-6039/transitions HTTP/1.0" 400 129 311 "-" "-" "1npdvvk"
And then I see an except in atlassian-jira.log, like this...
2017-10-08 19:55:11,459 https-jsse-nio-8443-exec-22 ERROR aratouser 1195x23640x2 daukzn 10.20.135.142,127.0.0.1 /rest/api/2/issue/ARATO-6044/transitions [c.a.jira.workflow.OSWorkflowManager] Caught exception while attempting to perform action 11 from workflow 42141 on issue 'ARATO-6044'
com.opensymphony.workflow.StoreException: Error marking step #335416 finished: root cause: Tried to update an entity that does not exist.
... etc ...
I checked the workflows and ran an IntegrityCheck in the webUI.
And checked the transitions for the issue via the API... e.g.
Is there anywhere else I can check to find out what "entity" that API call is trying to update, that doesn't exist?
Sorry to hear you are having this error. I'd recommend checking out this KB: JIRA Toolkit Auto Transition Listener fails due to InvalidActionException
You might not be using this Jira Toolkit in your instance, but the troubleshooting steps in that KB should help identify the problem here. Since you're seeing that error, it means that either something is wrong with the issue type, or with the workflow itself.
I'd recommend going into the project where this workflow exists, then edit that workflow. Then switch from Diagram mode into Text mode. The text mode will show Step names and Transitions that both include ID numbers like (11). In your case, action (11) refers to the transition in that workflow with the number (11). It's a good place to start there and check all the validators/conditions of that transition to make sure that these validators are not being held up because say a plugin that provides those transitions is not currently installed in Jira.
That's one possible cause, but it's too difficult to say for sure what is causing this without looking closely at the workflow.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs