The Proforma automation rule is not triggered on status update
Platform Notice: Data Center Only - This article only applies to Atlassian apps on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
A Proforma automation rule that is configured to add a form to a JSM (Jira Service Management) issue based on a status update is not triggered: when the JSM issue is transitioned, no form is added to it.
Environment
Jira Service Management (JSM) Server/Data Center, on any version from 8.0.0
ProForma: Forms & Checklist for Jira, on any version
Diagnosis
The Proforma form is configured with an automation rule:
The rule is configured to be triggered when the issue is transitioned to a specific status ("Waiting for customer", in the example below):
Checking the history tab of the JSM issue, we can see that it was transitioned several times to that status:
Checking the forms tab of the JSM issue, we can see that only 1 form is attached to it, and this form was attached at the issue creation time not when the issue was transitioned:
Checking the post-functions from the workflow transition that links to the destination status, we can see that an event which is not the Generic Event is fired:
Cause
As mentioned in the documentation Add a form on status change:
ProForma automation is currently configured to only fire automation on generic events. Integration with other event types will be added in the future.
If a different event than the Generic Event is fired in the transition, the Proforma automation will not be triggered.
We do have an open feature request to allow this automation to be triggered on other event types, which is tracked in https://jira.atlassian.com/browse/FORMDC-805, and which will be processed in accordance with our Implementation of New Features Policy.
Solution
Modify the post-functions in the workflow transition, so that the Generic Event is fired by the transition:
Was this helpful?