Redmine

This might be related to #6847 and it's related issues (especially #5880)...

I've created a pull request here to fix this issue.

+1 I've got the same problem too, with all fields that are calculated for parent tickets.

Tickets #6847 and #5880 should be unrelated to this ticket.

The problem can be traced to the leaf? call which is provided by the awesome_nested_set plugin. This in turn relies on the lft and rgt fields of the issue, which are apparently not updated when a child is lost. Andy Dufilie's patch on github seems to do The Right Thing by forcing an update of these fields upon deletion.

For those trying out Andy's patch: I can confirm it works, but with the following caveat:

Tickets whose fields you once made uneditable due to child creation and deletion will not be fixed by this patch, nor by re-creating and re-deleting a child for such a ticket.

You may try to manually fix the lft and rgt fields, but this is not obvious to me for a deeply nested leaf ticket; or you may duplicate the ticket and delete the old one (beware if your ticket has been referenced a lot).

I would really like to see this given a higher priority as having critical issues changed in priority to low automatically via the subtasking logic and and not being able to change them back is awful for reporting and production management purposes.

D@mn, now I remember seeing r7814 for #9577. I'll test later if this got actually fixed already.