$customHeader
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Problem

I have configured several JMWE post-functions on a single transition, in a specific order, but the post-functions seem to be running in a different order when I trigger the transition.

This can be a problem in certain cases. For example, if one post-function copies the "Affects Version/s" field from the parent issue of the subtask being transitioned, and then a second post-function copies the "Affects Version/s" field of that subtask to the "Fix Version/s" field, it will not work if the execution order of the two post-functions is reversed.

Solution

Due to the way non-native post functions (those provided by add-ons) are implemented in JIRA Cloud, it is not possible to guarantee the order in which post functions will be executed. Therefore, if your workflow incorporates post-functions provided by the JMWE add-on, you should ensure that your workflows do not depend on post-functions being executed in a specific order.


  • No labels