Our new Appfire Documentation Space is now live!
Take a look here! If you have any questions please email support@appfire.com
Placing post-functions in a transition
The position of a post-function in the list of post-functions for a transition is an important factor for its proper execution. When adding a new post-function to a transition, you must move it to the appropriate position, which depends on the type of transition ( Create or regular) and the type of post-function you configure.
On the Create transition
You need to place any JMWE post-function after the Creates the issue originally built-in post-function. Failure to do so will result in the creation of new issues raising an error (see https://ecosystem.atlassian.net/browse/ACJIRA-961 for details).
On any regular transition
On a regular transition, most post-functions can be placed anywhere in the list, except for the post-functions that transition issues (see below). However, it is advisable to always move them to the bottom of the list anyway.
Transition Current Issue, Transition Parent Issue, Transition Linked Issues post-functions
Post-functions that automatically transition issues should always be placed at the end of the list of post-functions. This applies to the following post-functions:
Random post-function execution order
Due to the asynchronous nature of Connect post-functions, it is not possible to guarantee the order in which post-functions are executed. Therefore, you should ensure that your workflows do not depend on post-functions being executed in a specific order. You can handle this using either the Delayed execution or the Sequence of post-functions post-function to sure that a series of post-functions run in a predictable order during a transition
Post-function outcome may not be visible immediately
JMWE post-functions are processed remotely and communicate back with Jira to update the issue. This helps ensure the stability and performance of your Jira Cloud instance; however, this also means that some updates may occur in the background after the view issue page has reloaded. A workaround is to enable the "Auto-refresh Issue" feature in the JMWE Configuration page which auto-refreshes the View Issue Screen if a change made by a JMWE post-function is detected within 10 seconds after the Transition completes.