On 02/06/2014 04:22 AM, Kristian Nørgaard wrote:
*In what way should I use and interpret "estimatedhours"?*
I have tried 3 different approaches:
1. Interpret "estimatedhours" as a dynamically changed field, in the
meaning of "most recently estimated TOTAL time"
It seems odd to re-estimate with a total time, maybe you already worked
100 hours on a ticket, then the obvious thing you want to do is estimate
how many hours are left (not the total).
This is how we use it. It may seem odd to you, but never seemed odd to
us, so the oddity is not universal.
3. Interpret "estimatedhours" as a fixed field, in the meaning of
"INITIAL estimated total time".
This doesn't make much sense for the various graphs unless you add
another custom field "remaininghours" to mean the "recently estimated
remaining time".
Our reports often find the first change to the estimatedhours field
which makes it a nonzero value, for estimate accuracy analysis at
project end. In a sense, this is a derived value.
So either I am not understanding these things right or everyone is just
accepting to live with such inconsistencies?
We don't see 1 as an inconsistency.
--
Matthew Caron, Software Build Engineer
Red Lion Controls | www.redlion.net
+1 (518) 877-5173 x138 office
--
You received this message because you are subscribed to the Google Groups "Trac
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/groups/opt_out.
