Our new Appfire Documentation Space is now live!

Take a look here! If you have any questions please email support@appfire.com

Preconditions for Post Functions

Owned by IT Ops Notifications
Last updated: Aug 09, 2022 by Deborah Scott (Unlicensed)
3 min read

This is the documentation for JSU for Jira Cloud. If you are using JSU on Jira Server or on Jira Data Center, see this use case in the Server/Data Center documentation.

Preconditions allow you to execute a post function only under certain circumstances. This helps you create more complex behaviors on your post functions, enabling Jira to do more work for you. In JSU Cloud, preconditions are part of the post function configuration.

The following use case explains how to get started with JSU preconditions for post functions.

Goal

Automate your budget approval issues

Scenario

You want to organize your budget approval issues using a project component.

We will use the Update Any Issue Field post function to set the issue component to Budget, ONLY IF:

  • the issue summary contains the word budget and;

  • the issue type is Story.

Let's have a look at how this can be automated using preconditions with JSU.

Components

 

How to configure this rule

  1. Create a draft of your project workflow. If you're unsure how to get to this page, follow the onboarding steps in Edit a Jira Workflow. You can then view your workflow in Text or Diagram mode. The steps in this use case represent Diagram mode. If you haven't already, switch the workflow viewer to Diagram mode.

  2. We want our automation to be executed on the Create transition, so we select the arrow that points to To Do to display the Options menu.

  3. Select Post Functions then select Add Post Function to display the list of available post functions.

  4. Select the Update Any Issue Field (JSU) post function then select Add at the bottom of the page.

  5. On the post function configuration page, select Add Precondition.

    Choose precondition page

  6. We want our preconditions to ensure that only issues with issue type, Story and a Summary containing budget text should be targeted for our post function execution. 

    1. Add the Value field precondition, and set Issue Type = Story

    2. Add the JQL precondition, and define a query to ensure that only issues containing budget in their summary will be found e.g. key={issue.key} AND summary~budget.

      You can configure the above preconditions using only JQL. In this case, the search query would be: key={issue.key} AND summary~budget AND issuetype=Story. Use a configuration method that is simplest for you.
      Always include the query key={issue.key} (or similar) on your JQL condition. This ensures that JQL is performed on the current issue. For more details see JQL Precondition.

      Precondition configuration page

  7. Configure the post function.

    1. Preconditions must be: set this to True.

    2. Update field on all issues related as: select Within same issue.

    3. Issue Field: select Component.

    4. Field Value: enter Budget.

  8. Select Add at the bottom of the page.

  9. Publish the workflow.

Test the rule

  1. To test our rule, we create an issue with issue type Story and call it Budget for Hardware. When we reload the issue, we can see that JSU updated it with the component Budget.

     

Demo Video

Watch the demo below to view this rule in action.

Need more information or help? Check out the JSU topic for preconditions for post functions or get in touch!