Opened 20 years ago
Closed 20 years ago
#1079 closed enhancement (duplicate)
add "Estimated Time" to ticket
Reported by: | Owned by: | Jonas Borgström | |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | ticket system | Version: | |
Severity: | normal | Keywords: | |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
A very useful feature would be a numeric box on a ticket for "Estimated Time for completion." Unit of meause would be either hours or days. Roadmap would include these values as a "Time remaining" total. Would be useful for practioners of agile development methodolgies such as SCRUM which track a "Burndown" value of the amount of work remaining.
Ambitious: A graph of this data tracking the change the totals over time would be ideal. I don't expect this to happen but at least tracking the data would allow creating the graph manually. Perhaps trac could allow exporting the data as tabular data into other software. An example can be found on the aforementioned SCRUM site: http://www.controlchaos.com/images/diagram/burndown.gif
Attachments (0)
Change History (2)
comment:1 by , 20 years ago
comment:2 by , 20 years ago
Resolution: | → duplicate |
---|---|
Status: | new → closed |
Manuzhai, I think the proposed "Estimated time for completion" field is supposed to be set by the ticket owner, and not somehow magically calculated.
Anyway, this is a duplicate of #710 I think (which is currently marked as wontfix). 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.
And how, do you propose, does this estimated time of completion get calculated?