Post functions in ScriptRunner for Jira Cloud are implemented as asynchronous webhooks. This means that:

  • Post functions cannot cancel a transition.

  • The issue may be displayed to the user before all the post functions have executed. ScriptRunner attempts to indicate to the user that the issue has been updated in the background, but this is not guaranteed.
  • Ordering of post function execution is not defined (you cannot have one post function rely on the output of another).

  • If you add a post function for creating a transition then it must be ordered below the post function named 'Re-index an issue to keep indexes in sync with the database' to ensure the issue gets created before the post function runs.