Feature #5876

Changes to child estimates should trigger journal entries for the parent estimate

Added by saturntechweb saturntechweb over 7 years ago. Updated over 7 years ago.

Status:ClosedStart date:2010-07-12
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:Issues
Target version:-
Resolution:Duplicate

Description

With the new 'subtask' feature in Redmine 1.0.0 RC, any existing estimate for an issue is replaced with a rollup of the estimates for the child issues. Some problems arise from this:
  1. Journal entries are created for estimate changes to the child issues, but not for the parent issue, which makes historical burnup reporting much more difficult.
  2. More importantly, any high-level estimate which once existed for a parent issue is lost once it gains a child issue. This is the only case I know of in the Redmine database where data gets lost without a journal entry.

Selfishly I only care about estimated time, although I assume this also affects the other rollup values: priority, start date and due date.

In other words, to reproduce:
1) Create issue
2) Set estimated time to 100
3) Create subtask
4) Set estimated time for subtask to 44

In the database, note that estimated_hours for the parent issue will have changed, but there is no associated journal entry.


Related issues

Duplicates Redmine - Feature #5875: Changes to child estimates should trigger journal entries... New 2010-07-12

History

#1 Updated by Holger Just over 7 years ago

  • Status changed from New to Closed
  • Resolution set to Duplicate

Please use http://demo.redmine.org for testing.

Also available in: Atom PDF