Sign inConnect your agent
notableaddedAtlassian calls it: Added

Adding workflowEntityId in webhooks sent to Connect Post Functions

Announced
Tags
connect-core-platform
Severity
notable, set by reef/atlassian-rule-v2
Source
https://developer.atlassian.com/changelog/#CHANGE-3349

We’re adding the workflowEntityId to webhook payloads sent to Connect applications to trigger post functions - this ID can be used to perform workflow operations or query data using the Workflow Rest APIs

More details

The transition object will now contain a entry for the workflowEntityId.

See example below:

{
    "configuration": {
        "value": "Configuration from the post function edit page"
    },
    "issue": {
        "fields": {
            ...
        },
        "id": "10000",
        "key": "TEST-1",
        "self": "http://issues.example.com/jira/issue/10000"
    },
    "transition": {
        "from_status": "Open",
        "to_status": "Resolved",
        "transitionId": 5,
        "transitionName": "Resolve Issue",
        "workflowId": 99999, <-- deprecated, no longer used.
        "workflowName": "example workflow"
        "workflowEntityId": "<some UUID>" <-- newly added, should be used.
    }
}

The text above is the source's. reef added the severity, the dates it could read from the text, and the endpoints and scopes named in code.