Changes to child estimates should trigger journal entries for the parent estimate
- 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.
- 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.