I offer paid 30 mins or 60 mins 1-1 consultancy calls.
Jira Courses, Training and Consulting: Sparxsys Trainings
Thanks for coming here, I hope you are enjoying learning here, I have also written some books in case you want to learn a bit more :)
If you need my help with Drupal, Linux, Jira, Scripting, Automation or want to contact me then raise a ticket for me please :) and I will get back to you, promise. At Sparxsys we provide Atlassian consultancy services, reach out to me at ravi at sparxsys dot com

Tutorial: Mastering Jira Automation Variables

In our recent tutorial session, we explored the powerful yet frequently overlooked "Create Variable" action in Jira Cloud Automation. Understanding how to use these variables is a game-changer for administrators looking to create cleaner, more maintainable automation rules.

The Problem: Repetitive Data Entry

Often, automation rules require referencing identical information—like release versions—multiple times. Without variables, this leads to long, hard-to-read rules that are difficult to update. Aaditya Kumar demonstrated that by storing data in a variable, you can reference it anywhere in your rule, much like coding, which simplifies maintenance significantly.

Getting Started with Variables

The tutorial walked through creating a flow using the "Create Variable" action. Key takeaways included:

  • Descriptive Naming: Always use meaningful names (e.g., "current version") rather than generic labels like "var one."
  • Dynamic Values: While the demo used hardcoded values for simplicity, these variables are designed to hold dynamic data derived from custom fields or smart values.
  • Smart Value Syntax: Variables are accessed using standard smart value syntax, making them easy to integrate into existing workflows.

Advanced Capabilities: Calculations and Manipulation

Variables are more than just static text. Because they function as smart values, you can:

  • Perform String Manipulation: Extract specific data, like the last two digits of a year (e.g., using "26" from "January 2026").
  • Execute Math: Convert values into numerical formats to calculate past or future release years (e.g., adding or subtracting years).

Best Practices for Success

  • Temporary Lifespan: Remember that variables only exist for the duration of the automation rule's execution.
  • Testing: As seen during the session, small spelling errors in variable names can break rule execution. Always double-check your configuration.

By implementing these best practices, Jira administrators can build more efficient, readable, and scalable automation rules. For those interested in expanding their Jira capabilities further, check out the resources on Forge applications linked in the video description.

Subscribe

* indicates required

Please confirm that you would like to from Sparxsys:

You can unsubscribe at any time by clicking the link in the footer of our emails. For information about our privacy practices, please visit our website.

We use Mailchimp as our marketing platform. By clicking below to subscribe, you acknowledge that your information will be transferred to Mailchimp for processing. Learn more about Mailchimp's privacy practices.

Want to contact me?