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,555,693
Community Members
 
Community Events
184
Community Groups

Calculate number of child issues per status category for an epic

I have added three numeric custom fields to an epic:

  • Derived: ToDo
  • Derived: In Progress
  • Derived: Done

I would like to create automation rules to calculate the total number of issues for each field based on the status category of the derived/child issues. One trigger would be whenever an issue is added/removed to the epic and the other one, when the status of one of the child issues changes.

I played around a bit, but couldn't get it to work. Any ideas?

1 answer

0 votes
nmenere
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Sep 13, 2020

Hi,

In Jira Cloud we have recently introduced a "Lookup issues" action that allows you to lookup issues via JQL and then reference them later in the rule as a smart-value.

With this you could have a rule:

  • When issue created
  • Branch on Epic
    • Lookup issues where jql: "Epic link" = "{{issue.key}}" and statusCategory = new
    • Edit issue - set "Derived:ToDo" to {{lookupIssues.size}}

 

Does that work for you?

 

Cheers,
Nick Menere [Atlassian]

That sounds promising, but we are using Jira Server. Will this be available there too?

nmenere
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Sep 20, 2020

Unfortunately this is a Cloud only feature with no plan to migrate to the Server.

😞  Server users = 2nd class customers

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events