Philip Colmer
I have a workflow in xMatters that results in a Jira Service Desk request being created. When a user is notified, they can assign the xMatters event to themselves and this also assigns the JSD request to them.
What I'd like to be able to do is have the xMatters event terminated if the user working on the JSD request marks it as resolved. I've installed the Jira Server Workflow Template and configured it. I've created a webhook in Jira so that it triggers the "Terminate Events" URL from the Jira Server Workflow.
I've then resolved a Service Desk ticket that was created by the first xMatters workflow but that action in JSD has not resulted in the corresponding xMatters event being marked as ended.
What am I misunderstanding here?
Thanks.
Philip
0
Comments
Please sign in to leave a comment.
Oh yes sorry, as a built-in it is that Activity Stream view that as you say is completely empty. I think that Jira must not be hitting the URL of the Terminate Events inbound in that case, with logging on like that you should get something in there whether it works or not. Are you sure the webhook in Jira is firing?
I believe the code underlying the terminate event process looks for an xMatters event with a matching Jira issue ID.
It sounds like the event you want to terminate is actually the initial event that initiated the whole process. Can you confirm if my understanding is correct? If so, that initial event probably doesn't have the issue ID in its properties so the terminate code won't be able to find it.
At the moment, this is not going to work. As far as I can tell, the webhook is not firing correctly at Jira's end. There is a known issue (https://jira.atlassian.com/browse/JRASERVER-65174) which, unfortunately, is now over 2 years old and Atlassian are "gathering impact".
Ho hum.
Thanks for the suggestions made, though. If I ever get the webhook firing, I'll come back to this.
Hey Philip,
I looked over the JIRA issue you posted, and it sounds like you are using Jira status to filter issues using JQL in the web hook? For example,
There may be some alternative solutions to workaround the bug.
1. Historical Operators
I wonder if using the historical operators might help solve the issue?
2. Using a resolution field
I've seen other solutions that replace the Jira Status with some other fields. For example, the resolution date having a value
or based on a specific resolution value
3. Use a customer Field and Workflow Post Action
If those don't work, you could track the state changes using Jira workflow and custom fields.
Hope this helps,
Craig