First try at webhook - custom field is missing, to_status is null

[Greg Bryant]

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?

"transition": {
"workflowId": 10004,
"workflowName": "File Load Error Workflow",
"transitionId": 21,
"transitionName": "Checked In",
"from_status": "In Progress",
"to_status": "null"
},

Thanks,

Greg

[Greg Bryant]

No, it's annoying, but we just ended up having to have an external lookup table to map these in (better than hardcoding, but really a huge defect in the webhook data fields).

[Sebastian Wilhelm]

Hey Greg have you found a way for renaming customfield_{id} into something more useable?

[Greg Bryant]

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.