Automation in Jira Cloud is a powerful tool, but it often requires fine-tuning to ensure it serves the team rather than creating unnecessary work. In a recent tutorial, Aaditya Kumar demonstrated how to build a precise automation flow that creates work items for new project versions while intelligently filtering out "noise" from internal-only testing versions.
This guide breaks down the technical configuration required to build a cleaner, more effective release pipeline.
The Challenge: Preventing Unwanted Automated Tasks
When setting up automation, a common pain point is the automatic creation of tasks for every version created. If a team frequently creates internal versions for training, testing, or internal tracking (often labeled "no release"), the board quickly becomes cluttered with irrelevant work items. The goal is to build an automation rule that only triggers when a meaningful version is created.
Step 1: Configuring the "Version Created" Trigger
The foundation of this workflow is the "version created" trigger, found within the Jira automation settings. This trigger acts as a listener, executing the automation rule every time a new version is added to the project.
Step 2: Implementing Advanced Filtering
To stop the automation from acting on internal versions, you must implement a conditional layer using "smart values" and regular expressions (regex).
- Smart Values Condition: Set the first value to version.name.
- Applying Regex: Configure the condition so that the version name must not match your designated regular expression.
- The Power of Syntax: The regex used here is key. It should be configured for case-insensitivity to catch variations like "No Release" vs "no release." Additionally, including \s components allows the rule to flexibly handle spacing, ensuring it matches the target phrase regardless of whether there is a space between the words.
Step 3: Defining Automated Actions
Once the automation confirms the version is valid, you can trigger specific actions.
- Issue Creation: Create a new work item (e.g., Task, Story, Epic, or Bug). A best practice is to use a smart value expression for the summary field, such as "new version is created: {{version.name}}." This keeps the task title dynamic and informative.
- Debugging with Log Actions: An essential, often overlooked step is adding a "log action." This action writes data into the automation audit log without modifying any issues. By setting the log to display the version name, administrators gain a verifiable trail to troubleshoot execution data or confirm why a specific version triggered (or didn't trigger) the rule.
Step 4: Validating the Pipeline
Testing is vital to ensure your regex filter functions as intended. Adopt a dual-testing approach:
- Positive Testing: Create a valid version (e.g., "tutorials"). The audit log should confirm that the condition passed and the task was successfully created.
- Negative Testing: Create an excluded version (e.g., "no release"). The log should reflect that the rule executed but performed zero actions because the input matched the prohibited regular expression.
Strategic Release Automation
While version creation is a great starting point, Jira’s automation capabilities extend far beyond this single trigger. Teams can leverage similar logic for other version-related events, including:
- Version deleted
- Version released
- Version unreleased
- Version updated
By combining these triggers with diverse administrative actions—such as sending automated emails, posting notifications to Slack channels, calling external webhooks, or updating existing issues—organizations can automate their entire end-to-end release process, ensuring that administration is scalable, clean, and highly efficient.
