We have a Time Tracking which has Original Estimated and the system has Due Date built-in field. If we estimate a ticket and set a due date, does it make sense or we just need one of them?
Hi,
Due Date is used to determine the last date a task should be complete.
Original Estimate (Time Tracking) used to determine how much time it will take to finish the task.
So for example:
You have a feature, your managers says this should be done by the end of Q1 (31 Mar), this is your due date.
You are looking at the task and says "ok, it will take 20 days of work", this is your original estimate.
So according to your estimation, you will finish the task long before the due date.
Is it clear now?
Hi @Nir Haimov,
In case Due Date and Estimated Time don't match each other, how could we solve it?
Hi @Tai Lam Phat,
They don't have to match each other, it's ok if they are different, so there is nothing to "solve" as this is not even an issue.
Example:
Today is Jan 29, you got 3 tasks need to be finished by Feb 28 (this is your due date for each task of your 3 tasks)
Task #1 you mark with effort of 3 days.
Task #2 you mark with effort of 12 days.
Task #3 you mark with effort of 7 days.
You finished eah one and akk of them together before the dead line (due date).
So i don't see what is the problem?
"you will finish the task long before the due date", in this case, the due date doesn't help you anything, it also makes a little bit of pressure and uncomfortable on the developer who works on that ticket.
My question is it is necessary to have a due date or in case it has to be displayed, it's all about business or developer should care?
It looks like you're new here. Sign in or register to get started.
