On Thu, Oct 09, 2008 at 09:48:49AM -0700, [EMAIL PROTECTED] wrote: > > On Oct 9, 10:39 am, Jeff Hammel <[EMAIL PROTECTED]> wrote: > > I will respond to the TracHours side of thing, since I'm partially > > responsible for it. TracHours was designed to meet the specs of one of our > > staff (a project manager, for lack of a better term) who didn't like > > certain features of TAEP. Namely, he wanted: > > > > * no addition to ticket comments when hours were added (save when hours > > were added with a message) > > * ability to edit hours instead of adding negative hours > > * ability to add hours as someone else with sufficient permission > > * ability to add hours on dates other than today > > * ability to query hours across (local) trac instances > > * ability to build reports (queries, really) for people's hours > > > > So those are the motivating factors. TAEP is certainly more mature and has > > many more features, both built in and built as extensions, but I can't > > speak to it more than that (I'm a mere developer, no project manager me). > > We're using TracHours in house now, though honestly I don't know how > > heavily. > > > > Jeff Hammel > > The Open Planning Projecthttp://topp.openplans.org > > IRC: jhammel, k0s > > > > On Thu, Oct 09, 2008 at 08:21:03AM -0700, gctrekker wrote: > > > > > We are comparing the TimingAndEstimationPlugin (TAEP) and the > > > TracHoursPlugin (THP) and I am interested on what users of either of > > > these plugins like or dislike about them. I have not installed either > > > of them at this point. We want to record the Level Of Effort estimate > > > and time worked to help with during triage of milestones. > > > > > I am using the trac-post-commit-hook and would like to also capture > > > hours from svn commits. The TAEP has a modified trac-post-commit-hook > > > that captures the time and updates the tickets. Has anyone modified > > > the trac-post-commit-hook program to work with THP? > > > > > I would appreciate comments from the group. In searching the group I > > > have not found many comments about this. Thank you. > > Interesting. I have a few questions/comments about the TracHours > plugin, if you have the time: > - when clicking on the total hours for a milestone on your demo site > (total hours: 645...or soemthing) which calculates correctly I might > add: > the breakdown threw the following error: > "Oops… > Trac detected an internal error: > KeyError: 'to_year' > There was an internal error in Trac. It is recommended that you > inform your local Trac administrator and give him all the information > he needs to reproduce the issue. > The action that triggered the error was: > GET: /hours" > does this happen in the current version, and is it planned to be > fixed.
Fixed, I think. Didn't know about this one. > - is this compatible with the Timing and Estimation plugin for the > purposes of other plugins that rely on it? (assuming they only use > the total_hours and estimated_hours fields) I can't really answer that question. The fields are named the same, so maybe. But I can't say. > - what would it take to put back in the "add hours to ticket" option. > the issue with directly editing is it doesn't prevent you from adding > negative hours (ok, I think you can "add hours to ticket" with a > negative, but it's less obvious Nothing prevents you from adding negative hours now. I've ticketed something like this: http://trac.openplans.org/hours/ticket/22 > - can we get the hour updates to show in the ticket history even when > no comment is included? (is this configurable?) Not yet. Ticketed: http://trac.openplans.org/hours/ticket/23 > - any macro's planned to use this information and/or graph it. No plans, no. > - any plan for totals/summations in reports and queries? These are already displayed in /hours > - support for master tickets? (i.e., summation of esitmates/totals > for child tickets.) Would be cool: http://trac.openplans.org/hours/ticket/24 > Btw, I think it's a pretty darn good looking plugin so far. Similiar > to the way Agilo does it, but their calculations are a little more > advanced as they can operate on data from linked tickets, and do more > than just sum. I am digging it, I may give it a try over the Timing > and Estimation plugin if it proves compatible with the other plugins > that use this data to do other things (reports, etc.) particularly the > Mylyn plugin, which I don't actually use, but some here like that it > can update total hours for them. > > Nice work! Thanks Jeff --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
