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

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How to aggregate field values for issues in a sprint using Jira Automation?

I'm interested in calculating aggregate values using Jira Automation, basically sums of field values such as Story Points and Original Estimate/Remaining Estimate of issues that share a Sprint. Ideally, this would be done during sprint planning - therefore I would be able to know the aggregated original estimate for all issues.

As an example, consider Assignee A has selected 3 issues for 'Sprint X', each of them having various 'originalEstimate' values. I would like to know if Assignee A is overloaded in 'Sprint X', i.e. the sum of all 'originalEstimate' in days would be larger than 10 days (2wk sprint).

I've tried doing it this way, but I can clearly see that I cannot edit a created variable on the 'For JQL' loop. I've also tried using a 'Lookup Issues' loop, but that didn't accumulate 'originalEstimate' value.

Any ideas?


1 answer

Hi @Gezim Basha 

You are correct about no edit for created variables, which is why I suggested this:

...and, limited access to fields with lookupIssues, which is why I suggested this:

...and, created variables have scoping limits.  There is an article describing the use of created variables to preserve the value outside of a branch...but it only works when there is one-and-only-one issue for the branch.  Otherwise shadowing appears to clear the value repeatedly.

What work-arounds could you do instead...

  • Use a custom field or entity property to store the sum and repeatedly re-fetch in the rule loop and make additions/updates.  That will definitely be slow, and might lead to some unintended side effects.  (I am guessing the rule engine may not like the re-fetch with the asynchronous processing in a loop.) 
  • Try some dashboard gadgets and filters based upon the current sprint, or use a filter subscription to review the results after planning
  • Or, use the Excel or Google Sheets add-ons to pull the data live, and build your own report to use during sprint planning


Best regards,


Suggest an answer

Log in or Sign up to answer
Site Admin
Community showcase
Published in Jira

Announcing the waitlist for Jira Work Management

Hey there Cloud Community members! We’re excited to give you the first glimpse of the new home for business teams on Jira — Jira Work Management. Jira Work Management is the next generation of J...

159 views 3 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you