https://www.redmine.org/https://www.redmine.org/favicon.ico?16793021292010-07-15T14:01:31ZRedmineRedmine - Feature #5875: Changes to child estimates should trigger journal entries for the parent estimatehttps://www.redmine.org/issues/5875?journal_id=183532010-07-15T14:01:31ZKurt Christensen
<ul></ul><p>This is somewhat related to <a class="issue tracker-2 status-5 priority-5 priority-high2 closed" title="Feature: Option for independent subtask priority/start date/due date/done ratio (Closed)" href="https://www.redmine.org/issues/5490">#5490</a></p> Redmine - Feature #5875: Changes to child estimates should trigger journal entries for the parent estimatehttps://www.redmine.org/issues/5875?journal_id=203212010-09-15T16:11:04ZKurt Christensen
<ul></ul><p>Just wondering if anyone out there cares about this... I probably should have marked it as a defect rather than a feature, since it really does give surprising database behavior - changes in the child tasks clobber values which are normally journaled, and you can actually lose history. Seems bad.</p> Redmine - Feature #5875: Changes to child estimates should trigger journal entries for the parent estimatehttps://www.redmine.org/issues/5875?journal_id=225332010-11-18T16:33:35ZKurt Christensen
<ul></ul><p>Hellooooo...? Anyone care about this??</p> Redmine - Feature #5875: Changes to child estimates should trigger journal entries for the parent estimatehttps://www.redmine.org/issues/5875?journal_id=225422010-11-18T23:26:17ZMischa The Evil
<ul></ul><p>Kurt Christensen wrote:</p>
<blockquote>
<p>Hellooooo...? Anyone care about this??</p>
</blockquote>
<p>I do. See the related issue I filed as <a class="issue tracker-2 status-1 priority-4 priority-default" title="Feature: Making an issue a subtask leads to loss of issue-property values (New)" href="https://www.redmine.org/issues/6687">#6687</a>. I updated the related issues accordingly too.</p> Redmine - Feature #5875: Changes to child estimates should trigger journal entries for the parent estimatehttps://www.redmine.org/issues/5875?journal_id=229982010-12-04T14:34:35ZRandy Syring
<ul></ul><p>I am not sure I agree with just creating a journal entry. My use case is as follows: I have higher level estimates on larger chunks of the project. I then create sub-tasks as needed. But as this issue indicates, as soon as I add a sub-task with an estimate, I lose the estimate on the parent.</p>
<p>I think my solution would be to come up with a different way to show the sum of the child hours. I don't think wanting an estimate on a parent issue as well having a sum of estimated hours on child issues should be mutually exclusive. I guess, I would advocate for a different field entirely on the issue, something like "Estimated time (children): ..." and keep the current field "Estimated time".</p>
<p>If thats not possible or desired, a second idea would be to let the value in the parent' issues "Estimated time" field determine what is shown. If it has a value, show it. If its blank, and child issues have values, then go ahead and sum the children's values.</p> Redmine - Feature #5875: Changes to child estimates should trigger journal entries for the parent estimatehttps://www.redmine.org/issues/5875?journal_id=292242011-05-26T13:31:23ZSvein-Tore Griff With
<ul></ul><p>I think Randy has suggested the best approach for this.</p>
<p><em>something like "Estimated time (children): ..." and keep the current field "Estimated time".</em></p>