Defect #5265
timetracking: subtasks time is added to the main task
| Status: | Closed | Start date: | 2010-04-07 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | Time tracking | |||
| Target version: | 1.0.0 (RC) | |||
| Affected version: | devel | Resolution: | Fixed |
Description
time tracking works weird with subtasks.
I logged to demo.redmine.org and created 3 tasks in my "ace" project:
1) feature1 - no estimate - target release 6.2
subtasks for feature1:
2) bug1 - estimate 5 hours - target release 6.2
3) task1 - estimate 10 hours - target release 6.2
I see total estimated time on 6.2 roadmap is 30 hours.
feature1 consists of 2 tasks, which are 15 hours total. and I see the total time of 15 hours shown on "feature1" details page.
why is subtasks' time added to the main task's time itself on the roadmap?
I'm considering using Redmine for simple project planning and I'm curious if timetracking feature is something experimental or stable enough to be used in production.
version.rb.diff 
(530 Bytes)
Related issues
Associated revisions
Fixes calculation of version estimated hours with subtasks (#5265).
History
#2 Updated by Jeffrey Jones about 3 years ago
I have been using time-tracking with no problems on 0.9.3.
If course that doesn't have sub-tasks. This is a new feature that isn't released yet, I think the demo site uses the developmental trunk code.
#3 Updated by Jean-Philippe Lang about 3 years ago
- Status changed from New to Closed
- Target version set to 1.0.0 (RC)
- Affected version set to devel
- Resolution set to Fixed
The total estimated time for the version is fixed in r3633. It should now be 15.