We're trying a webhook to integrate JIRA into a processing path (or maybe vice versa), and missing some critical information. We added a custom field, call it fileId, that will be populated programmatically when a ticket is created. When the person working on the ticket is done, the transition triggers a webhook to a service that should then retry processing. However, that field is never sent. It is visible and set just looking at the issue in the issue browser. The second problem is that the "to_status" field in transition is marked as null, but it clearly has a new status. The latter we can work around using the workflowName and transitionName, but it seems odd. Any clues?
"workflowName": "File Load Error Workflow",
"transitionName": "Checked In",
"from_status": "In Progress",
Turns out it was there, just by internal id (i.e. "customfield_10000" instead of the label). Note that this is unusable, as it is a) not predictable, and b) extremely fragile - is there any guarantee these IDs won't change with a migration to a new version? Still don't know why the "to_status" comes through as null.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hi Community! My name is Amir and I’m on the Jira Service Desk product marketing team at Atlassian. Our team would love to understand how you’re leveraging our ecosystem for Jira Service Desk. Wha...
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