You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
30 second summary - we have shipped 6 new DevOps automation triggers for Jira automation that connect your ‘Build and Deploy' tools. These triggers allow you to connect natively with tools like Jenkins and Circle CI so Devs can update Jira less, you can have more transparency in your build process and everyone can avoid unnecessary meetings and updates. Sound good? Read on!
We recently released new DevOps automation triggers which allow you to easily connect your work from your Git provider (Bitbucket, Github, Gitlab) to Jira Cloud. It has been a crowd-pleaser to say the least. Devs are enjoying more ‘deep-focus’ time without the need to update Jira after writing code. Admins are getting 8 hours of sleep per night (made up stat) knowing Jira is 100% up to date. And all of this is done through an intuitive automation engine available to every Jira Cloud admin.
Our dedicated team has listened to the feedback from customers and we have now added further support with 6 new ‘Build and Deploy’ DevOps triggers to optimize your workflows even further. This means you can now connect Jira Cloud natively with tools like Jenkins, Circle CI and Octopus Deploy.
These new deployment triggers (Deployment status changed, successful, failed) and build triggers (Build status changed, successful, failed) get fired when changes associated to an issue get built or deployed in the linked build and deployment tools. You can add superpowers to these automation rules using smart values (meta-data) listed here. These can access additional information associated with the triggers.
The light bulbs might already be flashing in your head with ideas of how your team can take advantage of this. For inspiration, here are some early use cases we have seen below.
When a build fails in Jenkins, add a comment to the Jira issue and send a Slack message to the team channel.
When an issue is deployed on a staging environment, send a Microsoft Teams message to team QA channel
When a deployment fails, update the status of change request issue to “On Hold / Blocked”
Any admin can simply go into the automation section in Jira (screenshot below, will look slightly different in next-gen projects). Start creating a rule and you will see the new triggers available to you. You will need to link your CI and build integration to your Jira account so just follow the steps on screen. Once done, you are set.
The smart values are the most powerful part of automation and also the most challenging aspect to grasp. You can simply choose the smart values you want from our docs here or learn more about each individual trigger here.
If you are new to Jira automation, you are going to love it. You don’t need to be a developer to use it, it’s simply drag and drop at a basic level. Some users are saving their team more than 50 hours a month, which is kind of crazy! If you want to learn more about how to get started with the basics, I recommend watching our on-demand ‘getting started with automation’ webinar followed by the ‘advanced automation webinar’.
For those more in the DevOps world, we are also hosting a webinar with GitLab soon so register here to learn how best practices in how to automate across the two tools.
Yes indeed. More customers are discovering automation every day. It is freely available to every single Cloud admin. It is not available natively in Jira Server / Data Centre but there is now an app in the marketplace from an Atlassian partner.
Jira Premium users do have increased access to Global rules which allow you to automate across more than one project but every admin has unlimited single project automation rules.
We hope you enjoy these triggers. Our product team love hearing feedback (even the negatives!) so feel free to add any comments below. Happy automating 🙂
20 accepted answers