Man hours field for Tickets

[anonymous]

Tickets should get 'time planned' and 'time spent on ticket' fields, in man hours. Those values should be consulted for a milestone's progress bar. That feature would enable users to use the ticket/milestone system for planning development processes.

Personally I'd like to abuse the milestones as scrums, with associated tickets as work packages.

To that end it would be even better if a ticket had a 'date started', 'planned end date' and 'progress' field. In scrum it's vital to know every day which work package lags behind.

I also posted this in less detail on the FeatureRequests page.

[per.norman@…]

I think this would be very nice!

Now we have to follow up every ticket eiter by manually changing the description or by using Excel. Both ways have their flaws. With your solution it would be easy to generate time reports per ticket or milestone, which we have to do manually now.

[kisg]

Trac ticket work tracking patch (for 0.8-stable, revision 1283)

[kisg]

I attached an implementation of this feature to the ticket.

Features:

• Planned work and Actual work fields for the tickets
• Displays remaining work
• Actual work is not updated directly. In the Properties block a Spent work field was added. With this field you can add the work amount for every change in the ticket. The Actual work field will be updated automatically.
• The roadmap view shows a new progress bar if the new fields are filled out. It shows how much time was budgeted for the tickets targeted for the milestone and how much time was already spent on resolving the tickets.
• New report: Active Tickets over budget
• Documentation updated: TracRoadmap and TracTickets

[kisg]

You can contact me on the following address: gergely dot kis at siemens dot com

(Sorry, missed it in the last comment.)

[cmlenz]

This enhancement request has been raised a couple of times (see #710 and #1079), and certainly is valid. But, as I commented on #1079:

The problem with adding time tracking features is that it moves
Trac into the realm of software development/management processes
(such as scrum). However, a goal of Trac is to impose as little
process as possible.

Naturally there is a conflict between imposing and supporting
processes. The NewWorkflow proposal is pushing in the direction
of supporting more sophisticated workflows, while still allowing
them to be simple and painless.

Time tracking features won't go intro Trac as a default feature, simply because a lot of projects don't need them (like open-source projects like Trac itself). This feature really depends on the TracPluggableModules proposal, combined with some of the ideas from NewWorkflow, which would allow us to integrate such functionality.

It will certainly not go into the 0.8 branch, which is reserved for bugfixes (and maybe very minor enhancements).

I'm closing this ticket as duplicate of #710. But also, I'm reopening #710 because it has become obvious that people want time tracking.