Hi, Am Donnerstag, 6. Februar 2014 10:22:38 UTC+1 schrieb Kristian Nørgaard:
3. Interpret "estimatedhours" as a fixed field, in the meaning of "INITIAL > estimated total time". > I use this approach. I use 3 additional custom fields with the following meaning: 1. estimatedhours.label = originally planned time 2. remaininghours.label = currently estimated rest time 3. totalhours.label = sum of worked 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". > > But this solution does still not provide consistent interpretation: > > a) For custom queries TimingAndEstimationPlugin still sums up > "estimatedhours" - "totalhours", so this number will often be different > from the field "remainingtime" (though they claim to give you the same > information) > Not sure what you mean. Where does it sum up that difference? I just know the sum up in the ticket query result table but each column has it's own sum there, and there's no subtraction. > b) Also TracJsGanttPlugin can not show the actual situation since no > single field provides the "currently estimated total time" which would be > the input it needs for "fields.estimate" > I use a patch to TracJsGanttPlugin I've posted in https://trac-hacks.org/ticket/11549 now. The chart is computed based on the remaininghours, but the ticket bar length is equal to the estimatedhours. The inner black bar is totalhours against estimatedhours in percent. CU, F@lk -- 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.
