Defect #25056
closed
Parent task issue
0%
Description
Hi,
We found a "Parent task" issue by our user, please refer to the attachment.
Files
Related issues
Updated by Go MAEDA about 7 years ago
- Status changed from New to Closed
- Resolution set to Invalid
Things you pointed out are not defect.
- Priority field of a parent issue is calculated from subtasks by default. Changes are not displayed in history if calculated from subtasks.
- Related issues and parent issue are totally different things. A parent issue is not listed as related issues.
Updated by Steve Zhou about 7 years ago
- Status changed from Closed to Reopened
Thank you for your explanation.
Is it possible to add change logs in parent issue?
In fact, the priority was changed without any evidence.
Updated by Go MAEDA about 7 years ago
Steve Zhou wrote:
Is it possible to add change logs in parent issue?
In fact, the priority was changed without any evidence.
If you don't prefer auto calculation of the priority field, you can turn off it. Go "Administration" > "Settings" page and open "Issue Traking", set "Parent tasks attributes > Priority" to "Independent from subtasks".
With the setting, all priority changes should be made by manual operation and all changes are logged.
Updated by Go MAEDA about 7 years ago
- Status changed from Reopened to Closed
I would be happy if my post is useful for you.
Closing this issue.
Updated by Mischa The Evil about 7 years ago
Go MAEDA wrote:
Go, there remains a valid issue with the current implementation when using it with parent tasks attributes setting set to "calculated from subtasks" which, I think, is what the OP is trying to report here. See #6687. Example:Steve Zhou wrote:
Is it possible to add change logs in parent issue?
In fact, the priority was changed without any evidence.If you don't prefer auto calculation of the priority field, you can turn off it. Go "Administration" > "Settings" page and open "Issue Traking", set "Parent tasks attributes > Priority" to "Independent from subtasks".
With the setting, all priority changes should be made by manual operation and all changes are logged.
When you have two issues:
- issue1 (priority => normal, start_date => 01-01-2017, due_date => 31-12-2017, %-done => 10 %)
- issue2 (priority => immediate, start_date => 05-01-2017, due_date => 05-03-2017, %-done => 50 %)
- issue2 (priority => immediate, start_date => 05-01-2017, due_date => 05-03-2017, %-done => 50 %, parent => issue1)
- issue1 (priority => immediate, start_date => 05-01-2017, due_date => 05-03-2017, %-done => 50 %)
This shows that the conversion of root-issue to parent-issue leads to a silent loss of issue attribute values, which I think is a true problem.
Updated by Go MAEDA about 7 years ago
Mischa, thank you for your explanation.
I have been thinking that it is a design rather than a defect.
Can I set this issue as a duplicate of #6687?
Updated by Mischa The Evil about 7 years ago
- Is duplicate of Feature #6687: Making an issue a subtask leads to loss of issue-property values added
Updated by Mischa The Evil about 7 years ago
- Resolution changed from Invalid to Duplicate
Go MAEDA wrote:
I have been thinking that it is a design rather than a defect.
Well, the roll-up is expected, but I consider the silent loss of the attribute values a legit defect. I've seen several cases where this was considered as a blocker to using Redmine's subtasking features.
Can I set this issue as a duplicate of #6687?
It doesn't fit completely looking at the initial post of the OP, but it fits after OP's feedback. As such I'll set it as a duplicate. Thanks for your support.