0 h in Estimate field (During Mandatory Conditions)
The value 0 h is a valid entry for estimation field even if the field is mandatory. The question is - Is 0 an acceptable value for the estimate field? I
Cheers, Sunita |
Accepted answer
Geoffrey Clemm (30.1k●3●30●35)
| answered Jan 11 '12, 12:53 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
There are a few edge cases where a 0 cost task is useful.
For example, suppose you have a particular date where a whole set of tasks need to be done by, but you might need to move that date. One way to implement that would be to have a 0 cost task set for that date, and make all the other tasks predecessors of that task. When the date changes, just update the due date on that task. Cheers, Geoff On 1/11/2012 11:53 AM, sdinakar wrote: Hi Geoff, Sunita Dinakar selected this answer as the correct answer
|
2 other answers
Geoffrey Clemm (30.1k●3●30●35)
| answered Jan 11 '12, 10:08 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Yes, 0 is a valid value in the estimation field.
Cheers, Geoff On 1/11/2012 9:38 AM, sdinakar wrote: The value 0 h is a valid entry for estimation field even if the |
Hi Geoff,
Thank you for the reply. Could you please explain how 0 would be considered as a valid entry? Any task (work item) should be estimated against time. Cheers, Sunita Yes, 0 is a valid value in the estimation field. The value 0 h is a valid entry for estimation field even if the |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.