ST-2026-153 · API endpoints & versions
Jira workflow webhook workflowId becomes an unusable placeholder
From 19 July 2026, workflowId in two Jira workflow-post-function webhook payloads is a placeholder and will be removed after 31 July 2027.
Previous state
Webhook consumers could treat workflowId as identifying a Jira workflow.
Current state
workflowId returns an invalid placeholder in Connect Workflow Post Function and Trigger a webhook payloads; workflowName or workflowEntityId must be used.
Affected users
Who needs to care
Connect post functions and Jira workflow webhook handlers that read transition.workflowId.
Required response
What to do
Replace workflowId dependencies with workflowEntityId or the source-supported workflowName before removal.
Evidence boundary
What the source does not prove
The change is limited to workflowId in the two named webhook payload families; the field remains present but unusable until removal.
Lifecycle history
Dated event sequence
- Placeholder behaviour documented
workflowId became unusable and the replacement fields were documented.
- Removal boundary
Atlassian states removal occurs after this date.
Evidence ledger
First-party sources
- 01Atlassian — Jira Cloud platform changelog — workflowId webhook deprecations
Official Jira Cloud API changelog · 2026-07-19
Open official source ↗