Seems that at least RoadmapHoursPlugin does not have the configuration options that allows using "remaininghours" in stead of "estimatedhours". Am I on a path that violates some of the plugins dependencies?
/Kristian On Mon, Feb 3, 2014 at 5:17 PM, Kristian Nørgaard <[email protected]>wrote: > Thanks, good practice is exactly what I am looking for, examples of what > will work together and what won't. > If I end up documenting the setup I have, where would be a good place to > publish this? > > I am testing on a copy of our production setup, so I can do all the > experiments I want! > > Ok, so now I have the four custom fields as you list them: > totalhours, estimatedhours, remaininghours, hours > > And apart from T&E plugin updating the totalhours, I guess there is no > automatic interaction between these fields? > > in trac.ini I have: > [estimation-tools] > estimation_field = remaininghours > > [TracPM] > fields.estimate = remaininghours > fields.worked = totalhours > > It seems to work in my first short tests. > Is this a "good practice" setup? > > And your policy is then: > * estimatedhours are only changed up front, before the ticket work is > starting. > * remaininghours are updated as you go on > > And then hours are added through a post-commit hook? > Is it correct that the estimated/remaining hours are not touched by the > default post-commit hook? > (I am thinking of support for writing not only #123 (4) to indicate 4 > hours spent, but also #123 (4, 10) to indicate 10 hours are left) > > I think I have seen some places that worked hours were set to a negative > number. What is the semantics of that? > > Thanks, > Kristian > > > > > On Mon, Feb 3, 2014 at 1:43 PM, F@lk <[email protected]> wrote: > >> 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. >> > > -- 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.
