Remaining Estimates From Sub-Tasks

[Andrzej Paszek]

Hi There,

I hope you are well ! 

I am trying to set automation rule that will enable me to get hours logged into sub-tasks to my main story, so that remaining hours are decreasing.

I created below rule, but when this runs my hours spent are doubling. 

Is there anything I can do to ensure that when this rules runs worklog from sub-task is getting deleted ?

[Bert Dombrecht]

Hi @Andrzej Paszek

Maybe you don't need an automation for this.

Here's my observation, I hope this helps:

On the parent story 'Time tracking' field, check 'Include subtasks'. The logged time and remaining estimate will be the sum of for the subtasks.

If you don't estimate your parent story, it will be just the sum of the sub-task estimates minus the logged time on the sub-tasks. If you also add an estimate to your parent story, it will be: parent-original-estimate + sub-task-original-estimates - parent-logged-hours - sub-task-logged-hours.

Best regards,

Bert

[Gor Greyan]

Hi @Andrzej Paszek

Welcome to the Atlassian Community!

Here is the working version, tested on my side.


Trigger: Work Logged Created
Condition: Issuetype = Sub-Task

Create Variable: wlStarted - {{worklog.started}}

Create Variable: wlSecs - {{worklog.timeSpent}}

Branch: For Parent

Add Log Work: Time Spent - {{wlSecs}}
                         Date Started - {{wlStarted}}

Let me know if you have any questions.

[Andrzej Paszek]

Hi Gor,

Many thanks for warm welcome and your answer. 

I have re-created your set-up, but it works exactly the same way mine did. Once I log time on the sub-task the hours spent would be multiplying.

I was hoping to arrive at the set-up where if someone adds time to the sub-task let's say 1h, then on the story it will be reflected as 1h less of remaining time. Instead I have 2 hours added in (I am aware of tick-box) but using reporting tools such as eazybi would be tricky in this context.

Do you think there is a way to delete worklog on the sub-task once automation for remaining time is finished ?

[Gor Greyan]

Dear @Andrzej Paszek

Sorry, I wrongly understood your question :)

In this case, I think you can do that without automation.

Just no need to estimate the parent ticket, check the "Include subtaks" checkbox, which will calculate the sum of the sub-tasks' original estimate and time spent.
If you are also estimating the parent, you just need to divide the number by 2 :D

In our company, we are just estimating the sub-tasks and seeing the progress on the parent ticket.

Also, the same as @Bert Dombrecht suggests.

[Andrzej Paszek]

Hi Both, 

Thanks for your answers, however this isn't what I had in mind. 

My issue started with a need to create a burndown chart (in hours), however I noticed that sub-tasks are not reducing remaining estimated hours on main story if someone would log their working time against them. 

This is now resolved by having the automation from Gor's example above in place.

My 2nd issue is that, we also have different reports that are using hours spent measure. Which in case, having above automation in place would inflate the numbers on the reports if anyone would put their time against the sub-task. 

So it sort of solves the issue, but opens up another. Hence me trying to find out if there is a way to not have time logged against the sub-tasks so it doesn't multiply the hours.

I am also aware of option to educate / inform the team to not log against sub-tasks and only do it for main story - which would solve the problem all together, but things happen and sometimes they do not. So I was looking for the way to take the issue away all together. 

I am bit surprised that this is intended Jira behaviour as seen many similar topics while researching for answers yesterday. 

Hopefully, this makes more sense now.