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

Automation rule with custom fields

why this rule does not run? do you have any suggestions?

Screen Shot 2018-08-24 at 3.01.43 PM.png


Victor Mutambuki _Mumo Systems_
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Aug 31, 2018


1. I noticed that the Issue types are different. One is spelt "request type" and the other "Request Type". Could this be an issue?

2. Have you enabled the Rule?


Jack Brickey
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Aug 31, 2018

The match legs are both failing and as Vic point out there should not be a difference in “request type” so I would edit both and it should give you the option to select request type vs. typing it in. Second I would have to guess that either the request type is not matching or the subsidiary is not in both cases. Are there other valid values and what is the action under those cases?

Hi Jack,

Thanks for your comments.

I checked and see that the request type is matching and the Subsidiary only has 3 values (QUOINE CORPORATION, QUOINE VN AND QUOINE PTE)

I edited the rule but it still does not run :(

Screen Shot 2018-09-05 at 10.59.18 AM.png

It still work if I separate this into two rules. Do you have any suggestions on this?


Log in or Sign up to comment
AUG Leaders

Atlassian Community Events