Actions
Patch #22345
closed
Trackers that have parent_issue_id in their disabled_core_fields should not be selectable for new child issues
Start date:
Due date:
% Done:
0%
Estimated time:
Description
When the user views an issue and clicks the link to add a new child issue, and the project has some trackers where the parent_issue_id field is disabled, the resulting new issue form for the child issue still presented those trackers for the user to choose from.
In case the tracker of the parent issue has parent_issue_id disabled itself, a new child issue would even have that tracker pre-selected through the tracker_id URL param, which is also fixed by the patch.
Patch extracted from Planio
Files
Related issues
Updated by Go MAEDA about 8 years ago
- File screenshot-without-the-patch.png screenshot-without-the-patch.png added
- Target version set to 3.3.0
Confirmed.
Setting target version to 3.3.0. Thanks for the patch.
Updated by Jean-Philippe Lang almost 8 years ago
- Status changed from New to Closed
- Assignee set to Jean-Philippe Lang
Committed, thanks.
Updated by Go MAEDA about 7 years ago
- Related to Defect #16260: Add Subtask does not work correctly from tasks with Parent Task field disabled added
Updated by Go MAEDA over 6 years ago
- Related to Defect #27895: Trackers with "Parent task" field set to "Read-only" should not be shown when adding a new subtask added
Actions