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

[Brellison]

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?

[Darryl Lee · Accepted solution]

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]

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

[Brellison]

Sweet! This fixes my problem. Thanks @Darryl Lee 

[Joseph Gardener]

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.

[Wenjia Tang]

Thanks so much for sharing the solution @Darryl Lee It helped a lot!

[Vinod Kotiya]

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.

[Yatish Madhav]

Thanks for the post and the comments, all. 

I have noticed many articles like this BUT it seems either something is missed or it is flying over my head :D

With trigger Work logged for all operations, does the update or delete of task worklogs reflect on the Epic? I noticed that if it is updated, the new time is added to the epic and if existing worklog is deleted, that same time is added to the Epic. Both of these seem incorrect. Also, it does not look like we can identify if it is added , updated or deleted.

Any idea please?

[Yatish Madhav]

Here is a screen grab.

The add work log, update work log and delete work log all log the time additionally to the Epic where it should actually add/update/delete accordingly. i.e expecting the Epic to have the same work log total as the child issues, but the Epic simple appends the total that is added, updated and delted as well.

Hope that helps in helping me :)

Thank you

[Aaron Geister]

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.