Hi, Am Montag, 3. Februar 2014 17:17:55 UTC+1 schrieb Kristian Nørgaard: > > 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? >
No idea. > > 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? > No, there isn't automatic interaction. It's up to you how to deal with the values in the fields. ...snip... > > It seems to work in my first short tests. > Is this a "good practice" setup? > Yes, looks good. > > And your policy is then: > * estimatedhours are only changed up front, before the ticket work is > starting. > * remaininghours are updated as you go on > Yep. I also add the worked hours manually from time to time, actually once in a week whenever I correct the remaininghours value. That's enough for my purposes. > > And then hours are added through a post-commit hook? > I don't use the post-commit hook for adding worked hours. Often I add hours after testing which is quite some time after the last commit. We found out, it's enough to add worked hours and correct the remaining hours right before a resource meeting, because then it should be up-to-date. 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.
