Picked form refuses to add during automation, no permission

[Martin Cleaver]

This makes no sense. I picked the form using the picker, but during a run it says that I don't have permission.

Work item created10/22/2025, 12:19:14

Attach forms10/22/2025, 12:19:15

Forms not attached

com.codebarrel.automation.component.proforma.api.error.explanations.no.permission

Send customized email10/22/2025, 12:19:15

If your organization has policies such as filter content or external user security (EUS), emails from this action may not be sent to some recipients. Contact your site admin or support if emails were not received.

[Martin Cleaver · Accepted solution]

It turned out that the actor, Automation for Jira, did not have access to Forms (how strange). Changing it to my own user worked. Life is short, so I moved on. Thanks to Bill though.

[Bill Sheboy]

Hi @Martin Cleaver 

One possible cause of this symptom is the known racetrack timing problem with the Work Item Created trigger (among others).  That is, the rule can start running before the work item data is fully available / stable for the rule to use, leading to incorrect conditions, actions, and weird errors...such as for permissions.  Atlassian knows about the defect and is working on architectural changes to address it...but with no timeframe announced.

The workarounds / mitigations for this defect are:

1. Always add the Re-fetch Work Item Data action immediately after that trigger.  This will slow the rule slightly, reloading the data before the steps proceed.
2. Do not use the new feature to add conditions directly to triggers.  Instead, add separate conditions after the re-fetch.

Only the first one applies to your rule, so please try adding the re-fetch and re-testing your rule.

Kind regards,
Bill