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,463,032
Community Members
 
Community Events
176
Community Groups

Sum up logged work on tasks to epic level - double counting entries

My goal: Create automation that will sum up the time spent entered on tasks to the epic level.

Problem: The below automation works... to an extent. If I enter 1h on a task within an epic, it will show 1h logged on the epic. If I log another 1h on the same task or another task within the same epic, then it will show 3h logged on the epic. This makes me believe the automation sums up all time spent entries (previous and new ones). Is there a way to get the automation to only sum up new time spent entries since the last time the automation was run?


Screen Shot 2022-04-26 at 1.54.55 PM.png

3 answers

1 accepted

4 votes
Answer accepted

Hi - so I see a few issues:

  • You probably want to add a condition so the rule only runs when you're logging time on a TASK.
  • You probably just need to add this value to Log work: {{worklog.timeSpent}} for the Epic and you don't have to Lookup anything.

So how this would work is:

You update task PROJECTX-123 which is part of epic PROJECTX-123.

  • Rule checks if it is a Task (because if it is an Epic, you would not want to double-log the time.)
  • If it is a Task, the For Epic (parent): Log work {{worklog.timeSpent}}

 

Darryl Lee Community Leader Apr 26, 2022

(You don't have to check for only Task. It can be any child-Issue Type.)

Screen Shot 2022-04-26 at 1.25.16 PM.png

Like Danielle Jackson likes this

Sweet! This fixes my problem. Thanks @Darryl Lee 

Like Dario Cali likes this

Is there a way for Subtasks to roll Up.  Currently my automation looks like this but the sub tasks time entry is not rolling up to EPIC.  Stories, Bugs and Task Issue Types work fine.  Just not sub tasks.

 

Time Entry Rollup.png

Like Aaron Geister likes this

Here is the solution to Rollup time spent to Epic Level. When time is lgged in Task/Stories and Subtask level.  Working perfectly fine.

First check is for non-Epic, a second check is for some subtasks.

Capture.PNG

0 votes

I am currently trying to get this same automation to work but when you make changes to the child issue time the audit logs show "NO ACTIONS PERFORMED"

It is the same automation as what is above.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events