Hi, Am Montag, 3. Februar 2014 12:00:07 UTC+1 schrieb Kristian Nørgaard: > > Will I have to perform database hacks also, as described in > http://trac-hacks.org/ticket/8681 > ??? >
the manual DB tweaking described in #8681 is just necessary in this situation: - firstly, you used only EstimationToolsPlugin with ticket field 'estimatedhours' in the meaning of "recently estimated rest time" - secondly, after a while you wanted to use also TimingAndEstimationPlugin or TracJsGanttPlugin and recognize they use 'estimatedhours' in the meaning of "originally planned time for the ticket" The issue reported in #8681 reports the clash of the meaning of that ticket-field, and suggests how you can overcome the problem. Kristian, the a good practice is to use these 3 ticket fields: [ticket-custom] totalhours = text totalhours.label = sum of worked time totalhours.value = 0 estimatedhours = text estimatedhours.label = originally planned time estimatedhours.value = 8 remaininghours = text remaininghours.label = currently estimated rest time remaininghours.value = 8 For example, estimatedhours could be 120 hours (your plan), and you have 100 totalhours (what you've worked so far), and you still judge 100 remaininghours (currently expected rest time). and T&E plugin also internally needs: hours = text hours.label = adds another time to totalhours hours.value = 0 Then the charts should properly work. 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.
