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,465,508
Community Members
 
Community Events
176
Community Groups

How to sumif estimates on specific sub-task types

I'm trying to sum numerical fields on sub-tasks at the parent level if the sub-task is of a particular sub-task type (we've setup new sub-task issue types).

I've managed to setup automation that sums up all sub-tasks regardless of sub-task type, but I need to be able to narrow it down further. Here's the snippet I use for the additional fields:

{
"fields": {
"Sum Back-end Estimates": {{issue.subtasks.Story Points.sum}}
}
}

 I want it to be more like

{
"fields": {
"Sum Back-end Estimates": {{issue.subtasks.Story Points.sumif(issue.subtasks.issueType.name,"Back-end Sub-Task")}}
}
}

2 answers

1 accepted

1 vote
Answer accepted

Hi @Michael G_ 

There are at least a couple of ways to do this:

  1. using JQL to find the subtasks you want (which have the trigger issue as parent), use the lookup issues action to gather and sum the values
  2. using an mathematical expression, an iterator on the subtasks, and conditional logic on the issueType, sum the values

I recommend trying the first one.

Kind regards,
Bill

Ah, using the look up action and then the corresponding {{lookupIssues}} resolved it. Thank you!

Like Bill Sheboy likes this

I need a similar thing, Michael can you post a screenshot or text of the rule that you ended up writing for this? I'm not 100% clear on how one can use the lookup issues function here. 

the general flow goes:

  1. When Value changes for {field}
  2. Issue Type is one of {sub-task}
  3. For Parent
    1. Then: Lookup issues: issuetype = "Sub-Task" AND parent = {{triggerIssue.parent}}
    2. And: Edit issue fields
{
"fields": {
"Sum Estimates": {{lookupIssues.Story Points.sum}}
}
}
Like Bill Sheboy likes this

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events