You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hello,
All of my stories and tasks in my backlog have a numerical value for the custom field "Total Size Days for Completion (exclu. A+D and Testing)".
For each epic related to my backlog, I would like to have an automation that adds up the Total Size Days custom field for all of the stories and tasks linked/under the epics. I would like the number that comes out of this sum to populate the custom field "Actual Days (Using Addition of Stories)" on my epics.
How do I go about doing this?
I have attached an image of what I have tried rule wise using this actual days formula at the end, but its not working
{{lookupIssues.Total Size Days for Completion (exclu. A+D and Testing).sum}
Hello @Lara M
Can you show us the Audit Log for an execution of the rule?
I believe the problem is in your Lookup Issues action. I believe the syntax is wrong. You have:
project=STWPOC and issuetype in (Story,Task) and "{{issue.Epic Link}}"
The last criteria is not valid syntax. It should be
project=STWPOC and issuetype in (Story,Task) and "Epic Link" = {{issue.Epic Link}}
Hi Trudy,
I updated the syntax what your wrote above and now its showing 'some errors'.
Please see the audit log below :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ah, yes, my apologies. Within the branch the context of the {{issue}} smart value has changed from the issue that triggered the rule to the Epic upon which you are branching. Epic Link within the Epic itself would be blank.
Before the "For Epic" step add a step to Create Variable.
Then within the For branch in the JQL for the Lookup Issues action use {{ParentEpicKey}} instead of {{issue.Epic Link}}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Trudy,
Thanks for your help. So to look like this? It's still making no changes to my epics :(
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Within the For branch in the JQL for the Lookup Issues action use {{ParentEpicKey}} instead of {{issue.Epic Link}}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.