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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

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!

Leaderboard

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
4,554,508
Community Members
 
Community Events
184
Community Groups

Weird behavior with slack automation

Hi All, 

I am trying to send slack messages to different channels based on field values. I am able to get several individual configuration to work, but when combined, it only sends the first slack message. 

 

Here is the detail. 

  1. If I don't do branching*, and the action is to send several slack messages, it works. 
  2. if I do branching, and the action is to update several field values for testing, rather than send slack messages, it works. 
  3. If I do branching, and only one branch is trigger, it works. 

But if I do branching, and trigger both branches, it only send the first slack message. 

Branching*: it's my understanding that Jira automation requires branching to run multiple evaluations without early termination. 

 

I really don't understand why this happens. Any help is appreciated. 

 

Thank you,

Zekai

 

 

Screenshot 2023-05-10 at 9.47.19 PM.pngScreenshot 2023-05-10 at 9.52.37 PM.png

 

1 answer

1 accepted

1 vote
Answer accepted

Finally got it to work. Something is weird with the AffectedService fields. If I use advanced comparison with smart values as opposed to directly using the field, the logic work. And I don't have to use the branches either. 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events