nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Estimation time is affected after more than one person's worklog entry in the same issue.

Adem Kaya_tz3dax

In the scenario where multiple individuals are working on the same task, worklog entries from different users are affecting the estimated times (Original Estimate and Remaining Estimate). For instance, I estimated a task to take 5 hours and worked on it for 4 hours. However, when another user logs a worklog entry for 2 hours, my estimated times are updated to a total of 6 hours. Yet, my initial estimation was 5 hours. How can I manage this situation in complex tasks involving different individuals? Since I cannot foresee such factors when planning tasks, how can I resolve this without disrupting the current person's plan?

Accepted answers

All comments

Jack Brickey

Hi @Adem Kaya ,

the original estimate should only change if you manually do so. Logging time will only affect actual time spent and remaining time based upon the original estimation. This is how Jira time logging works. I think that the fundamental issue here is that you have multiple people logging time on a single task. issues should really be owned by a single individual. If you want multiple individuals to work on a given task, then consider using sub-tasks for each individual. In this way, you can estimate the sub-tasks separately.

Antuan Sammak

Hi @Adem Kaya

I think there are two options that can be followed here:

1- have a more holistic planning in the beginning that involves all activities that need to be done on this ticket and ad original estimate accordingly, i wont recommend this because it would make reporting very hard and complicated.

2- when the work is complicated then keep this ticket as Parent and create different subtasks under it, each one represents different aspect of the work that is needed.

this way, you estimate your subtask and that gets automatically added to the parent ticket. then when your colleague needs to work on the same, another subtask to be created with its own estimation and time logging.

all the above will be reflected automatically in the parent fields.

Regards,

Adem Kaya_tz3dax

But there is a lot of work. For example, more than one person reviews the same job. Should each reviewer open a separate review sub-task? Is this sustainable? @Antuan Sammak @Jack Brickey

Jack Brickey

@Adem Kaya , if you don't wish to have individual sub-tasks for each person then ensure that your original estimation takes into consideration all of the actual work that's going to be done. If five people work on a task, and only one person provides an estimation then your estimation is incorrect.

Adem Kaya_tz3dax

Thanks for your suggestions.

Adem Kaya_tz3dax

Thanks for your suggestions

Antuan Sammak

@Adem Kaya in order to have an accurate time reporting this would be your best solution, its complicated in case you plan to create those subtasks manually. however, i do recommend using automation which will save you a lot of time.

another solution might be, is to create separate statuses in jira for each review stage then generate a report based on the time that was spent per status. this way you keep the estimation of the main task the same and you can log your time accordingly and the reviewers time will be calculated based on time spent on status.

hope the above helps.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud

time-tracking

estimate

worklog