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

Question regarding a manual trigger rule

Hi everyone,

I've created a manually triggered rule, however, it is not working as expectedScreenshot 2022-11-29 193328.pngScreenshot 2022-11-29 193715.png




The rule is to check for the same quote # and link if there is a matching quote #. When I run this rule manually, it is not giving the desired result. There is a matching quote # in the procurement test project, but the lookup returns empty. Please help


1 answer

1 accepted

0 votes
Answer accepted

Hi @Vishnu 

I recreated your rule in my test instance and it worked for me using '1234' as the custom field value, here are a couple of things I would try to narrow down the issue:

First, what I typically do when I'm not getting expected results from rules is start adding log actions to the rule. The log action outputs a value to the audit log for the rule so you can see what if any variables are stored in the smart values. In your case, I would add an action to log the value of {{triggerIssue.Quote #}} and {{lookupIssues}}.

Second, I would run the JQL using the value from {{triggerIssue.Quote  #}} to see if you get any results that way. If I had to guess at what the issue is, I'd guess it has something to do with the actual custom field value. Adding log actions to your rule will help you determine that.

Hello @Luis Machado 

Thanks for your quick reply.

Sorry, I'm not able to follow the steps you've mentioned. If possible can you share the screenshots of the rule, it would help me a lot. Thanks again

Certainly. So the action you would add is the 'Log action' action.

Screen Shot 2022-11-29 at 9.30.13 AM.png

Then you type out a message to include in the log and specify the smart value, I usually do something like <Name of the Smart Value>: {{SmartValue}}

Screen Shot 2022-11-29 at 9.39.57 AM.png

You'll want to add this action to your rule after the variable has been stored in the smart value. I typically do it before the smart value is used so it's in line with what I'm looking for:

Screen Shot 2022-11-29 at 9.31.55 AM.png


After you run the rule navigate back to the rule edit page and click on the Audit log -> "Show More" and then look for the 'Log action' lines that you previously configured.

Screen Shot 2022-11-29 at 9.32.23 AM.png

Like Bill Sheboy likes this

@Luis Machado - Thank you for your help

Like Luis Machado likes this

Suggest an answer

Log in or Sign up to answer