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
Hello, Data Center Community,
My name is Mel, I’m part of the Data Center marketing team, and I’m here to help you better automate work in Jira Software across teams, departments, and deployments. Jira Software alone can accomplish a ton, but when you take advantage of Automation for Jira (A4J), the possibilities are truly endless.
Don’t forget! A4J is natively included in Jira Software 9.0 Data Center and above—including the latest LTS release. If you’re running a version older than 9.0, the A4J app for Data Center is now a free marketplace app.
Check out these 3 tips on how to use automation to improve collaboration across teams:
Use A4J to automate issue creation from one Jira instance to another
“Smartly” leverage issue fields to clearly communicate with stakeholders
Leverage the audit log to monitor automated processes and keep workflows streamlined
1. Use A4J to automate issue creation from one Jira instance to another
Don’t let separate instances across your organization slow your work and silo your teams. Instead, use Automation for Jira (A4J) to configure your JSW and JSM instances to copy critical information across both instances.
Put simply, this rule tells the first Jira instance (the sender) to send a webhook when an issue is created. A4J allows you to set a rule within the second Jira instance (the receiver) to update issues according to the incoming webhook. Connecting these instances allows you to work more effectively across teams, regardless of deployment. Learn how.
2. “Smartly” leverage issue fields to clearly communicate with stakeholders
Updating issue fields and commenting on tickets is one of the most common uses for A4J. But the more your team uses automation, the more comments can appear on an issue, compounding in confusion if they aren’t written clearly. Smart values help keep those fields organized and clear to understand. As you can see in the example below, smart values take the comment from simply “we are now looking into your issue and will get back to you with an update” to a dynamic comment that tells the reader who is actively working on the issue.
This added layer of accountability and transparency opens the door for dialogue and helps teams better communicate and collaborate. Enterprise teams especially may find ticketing to be the only time some departments interact. Including names within comments not only makes the ticketing process more personable but also introduces a level of camaraderie and teamwork users may not otherwise experience. Learn more about smart values.
3. Leverage the audit log to monitor automated processes and keep workflows streamlined
As more people across more teams start to create rules, instances end up with a compounding number of automated processes that can start to slip through the cracks. Even within one team, it can become difficult to track all the automated processes built into Jira Software.
Don’t find yourself wondering which automation trigger resulted in what issue updates. The A4J audit log gives detailed insight into each automated action within your instance in the last 90 days. As your teams set up and expand their automated workflows, it’s recommended to check the audit log periodically to ensure everything works as expected. This is also the best first step in debugging A4J if you do notice a failure or unexpected behavior. Learn more about the audit log.
I hope these tips helped you automate your work across Atlassian products and deployments, allowing your whole organization to get the most out of Jira Software!