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,552,225
Community Members
 
Community Events
184
Community Groups

In automation, {{lookupIssues.Story Points.sum}}, when assigned to a variable is empty

For an automation rule, I have as my first component, an If JQL Condition query which returns a couple hundred issues that have story points.

Then I have a component that creates a variable called TotalStoryPoints from this smart value: {{lookupIssues.Story Points.sum}}

Then I have a component that logs the variable  TotalStoryPoints to the log

When I run the rule,  TotalStoryPoints is empty when I look in the audit log. 

Why does it not total up the story points for the issues from the JQL Query?

 

2 answers

1 accepted

0 votes
Answer accepted
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Apr 20, 2023

The {{lookupIssues}} smart value is populated only by the Lookup Issues action. If you have not used that action, the smart value is empty.

Do note that the Lookup Issue action is limited to returning only 100 issues.

https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Lookup-issues

The CONDITION If JQL Matches does not return a list that you can act upon. It is meant to check if an issue you already have in hand matches the conditions specified in the JQL.

That worked!  Thanks!

0 votes
Bill Sheboy
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.
Apr 20, 2023

Hi @Cash Coyne 

This seems the same/similar to the other question you recently posted here: https://community.atlassian.com/t5/Jira-questions/In-Jira-Automation-how-can-I-do-a-branch-and-then-come-back-to/qaq-p/2338351

I recommend posting images of your complete automation rule and the audit log details showing the rule execution.  That will provide context for the symptoms you describe and help the community to offer ideas.  Thanks!

Kind regards,
Bill

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