Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

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.

Deleted user Avatar
Deleted user

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.

Atlassian Community about banner
Community Members
Community Events
Community Groups

"Approval Completed" trigger component added to JSM Automation

Hi Everyone,

I would like to inform you that we have released the "Approval Completed Trigger" trigger in A4J (automation). Now automation rules can be triggered after an approval request is accepted or declined for an issue in Jira Service Management.

Read more:

  1. Approval Completed Trigger
  2. Smart Values Supported by Approval Completed Trigger

Makarand Gomashe
Product Manager, JSM


Dirk Ronsmans Community Leader Jan 20, 2022

Hi @Makarand Gomashe ,

I'm wondering how exactly this would be a better choice over the "Issue transitioned" trigger?

When an issue is approved or declined the first thing would be to transition it towards another status. Wouldn't that have the same effect?

Good nonetheless, just wondering what the difference might be :)

Like # people like this

Thanks @Makarand Gomashe for sharing this new feature.

I am also looking forward to the response to @Dirk Ronsmans query above as it would help providing more clarification on the usage of this new trigger.

For me, the 'Approval Completed Trigger' only makes sense when there is more than one 'Number of Approvers', i.e. 2 approvers needed on a particular status. In this case, I would expect the new trigger to be triggered on each Approval. However, this is not the case, it is only triggered after the final approval. This is an error. It should be triggered on the Approval of each person, then it is a useful function. 

Like # people like this


Log in or Sign up to comment

Atlassian Community Events