Earn badges and make progress
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
Next: Root
1 badge earned
Participate in fun challenges
Challenges come and go, but your rewards stay with you. Do more to earn more!
Gift kudos to your peers
What goes around comes around! Share the love by gifting kudos to your peers.
Rise up in the ranks
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Come for the products,
stay for the community
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
1 answer
Hi Daniel,
That should be possible. If your JSM integration is configured under a team, then the heartbeat should be configured under the same team as well. The integration would only trigger on alerts sent to that team.
You'd want to have the outgoing flow of the JSM integration create issues for these types of alerts. Here's a configuration I have that was successful in creating a JSM issue from a heartbeat alert. Both the integration and heartbeat are configured under my Community Team:
The JSM integration above is our legacy integration. The idea would be the same with the JSM cloud integration under the Outgoing automation rules section - if you are using this instead:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.