Add new subtask - parent issue id is lost in some cases
When the tracker of an issue has the
parent_issue_id field disabled and one tries to add a subtask, it may happen that the id of the parent gets lost if the tracker that gets preselected in the new issue form is the same or also has the
parent_issue_id field disabled.
The attached patch which we developed at Planio fixes this by always passing the id of a tracker with the
parent_issue_id field enabled (is possible at all) through the 'Add subtask' link.
#4 Updated by Go MAEDA about 1 month ago
I couldn't reproduce the problem (see the screenshots below). In Redmine 3.4, trackers whose "Parent task" field is disabled are not shown in the new issue form. It is because of #16260.
Could you show steps to reproduce?
#5 Updated by Felix Schäfer about 1 month ago
I am sorry it seems we did not test this thoroughly enough on Redmine 3.4.0, the fix for #16260 indeed also fixes this problem. The problem we encountered was the same problem you have described in #16260#note-7.
We also had debated fixing this as it has been fixed in r16383 but had decided against fixing this in the
issue.rb, as this introduces subtle differences in handling new issues. For example if you create a new issue using the API without a
tracker_id but with a
parent_issue_id, Redmine will automatically select a tracker that has not the parent issue field disabled. If you create a new issue using the API without a
tracker_id but with a
description, Redmine will not automatically select a tracker that has not the description field disabled. This means that
parent_issue_id will never be "lost", but
description can be lost. This is a discussion for another ticket and another time though :-)
I think this ticket can be closed as the original problem has been solved. Thank you for testing this and pointing out that it had already been fixed.
#6 Updated by Go MAEDA about 1 month ago
- Status changed from New to Closed
- Target version deleted (
I am closing this issue because we confirmed this issue had already been fixed by #16260 (Redmine 3.4.0).
Felix, thank you for investigation. I do appreciate that you and people from Planio have always made fabulous contributions to Redmine.