Jira automation templates for software teams
Software teams today are shipping quicker and better than ever before. Automation plays a key part in this.
From removing the small distractions that rip you out of your focus zone to bigger repetitive pieces of work that eat up precious development time, automation can help bring balance to any team. We have covered DevOps automation rules in a separate section but below are some of the most common rules used by software teams today.
Inform watchers of fixes / new releases
When a bug is fixed or a new feature is released, automatically inform any watchers
Transition relevant Jira issues upon a release
With every new cloud release, transition relevant Jira issues and let the team know via Slack
When an issue moves to ‘In Progress’ set the sprint to current
Balancing your work in your sprint is no easy task but automation can help keep things under control. Make sure anything currently being worked on is included in the current sprint.
.svg?cdnVersion=1479)
When any Jira issue has been marked as ‘Deployed to Cloud’ then transition it to ‘done’
Keeping Jira uncluttered is the secret to success. For this rule, use a scheduled trigger to find any issues in the wrong place and put them right.
Keep epic and linked issues in sync
If you have lots of stories in an epic, this rule will save lots of time. As soon as a story in an epic changes status, the epic will follow suit.
When a story is added to the current sprint, then email Jane
Make sure no sneaky work gets added to your sprint with automated notifications when an issue is added to the current sprint.
Learn more about Jira automation for software teams
Jira automation getting started guide
See all Jira automation resources in one place
Visit our Jira automation YouTube channel
Popular categories
Most popular automations
Jira + Slack / MS Teams
Jira + BitBucket, GitHub or Gitlab
Jira automation for business
