Moving issue to different project silently clears parent
We already know that the new subtasks feature only applies to issues in the same project. Even issues in subprojects of the current project are excluded, which seems to make little sense.
However today I discovered a corollary - if you take a subtask and 'Move' it to a subproject it has its parent field silently cleared. I understand that I have to choose between having it in the subtasks list OR having it in a different project, but I do not agree that this information should be silently cleared as many users will be unaware of this restriction.
Updated by Etienne Massip over 11 years ago
- Category set to Issues
Updated by Go MAEDA about 7 years ago
- Subject changed from Moving issue to different project clears parent to Moving issue to different project silently clears parent
This issue still remains in 3.2 if "Allow cross-project subtasks" is disabled.