Managing active Jira issues often means scrolling through dozens of comments from developers, testers, and project managers just to find the latest project update. This manual review process is time-consuming and can lead to missed information, especially when managing multiple work items daily.
Jira automation is a powerful tool, but true efficiency comes from mastering "smart values." These dynamic placeholders allow you to pull data directly from your tickets, turning static rules into intelligent, automated workflows. In this post, we’ll explore how to get started and troubleshoot common hurdles.
Using Jira Cloud to develop great products? Then use Automation to retrieve the details of the pull requests as well and send it to #Slack channels.
Title: {{pullRequest.title}}
Url: {{pullRequest.url}}
#Automation #PullRequest #Development #Bitbucket #Slack
There was a question on the community about negating a specific keyword using Regular Express.
Use case: You want to not run the Automation rule when a release is created with name "norelease".
So in this case when you created a new rule with Version created trigger then use the following regular expression.
^(?!.*norelease).*$
You can set your due date automatically based on creation date + 7 working days using {{issue.created.plusBusinessDays(7)}} #SmartValue
When using Automation for Jira you may use regular expressions along with Smart Values (if needed)
Use the "contain regular expression” condition to match for multiple keywords like this.
^(Keyword 1|Keyword 2|Keyword 3)
This will save time and makes your automation neat :)
You can fetch the last comment using {{issue.comments.last.body}} #SmartValues #Jira #Cloud #Automation
Ravi Sagar
ravi at sparxsys dot com
Author of "Mastering JIRA 7" book. Loves #Jira and #Drupal. #Blogger, #ProblemSolver, #Atlassian #Consultant and #Technologist @ravisagar on twitter
Want my help? raise a support request for me.
Social and other Links