Deploying automation with template form internal IDs.
This automation might reference forms by internal IDs that don't exist in the target Jira environment. Review and edit them if required.
Why this happens
Automations in Jira can be linked to forms via a property called templateFormIds, which contains an array of form numeric IDs (e.g., [1, 2, 3]). These IDs are system-generated and environment-specific, meaning that the same form will likely have a different ID in each Jira environment.
At the same time, Jira exposes forms through its API along with their UUIDs. These UUIDs are different from the numeric internal IDs used in templateFormIds, so we can’t reliably match them.
Even if the same form exists in both environments, the numeric IDs will differ - and there's no direct mapping between the two.
What it means for your deployment
If you:
Add a new automation that references forms
modify an existing automation's
templateFormIds
Then those internal form IDs will be deployed as-is to the target environment.
But since the target environment likely has different internal IDs for its forms, the automation may reference the wrong forms - or none at all.
What you should do
Edit the deployment:
Open the automation in the source Jira environment and check the list of forms
Check the relevant form IDs in the target Jira environment
By clicking on it and checking the ID in the url:
https://site.atlassian.net/jira/servicedesk/projects/PROJ/settings/forms/form/1/edit
Manually edit the templateFormIds list in the deployment accordingly
Fix in Jira post deploy:
Open the automation in the target Jira environment
Manually edit the associated forms under the automation settings.