Project

General

Profile

Actions

Defect #8376

open

Moving issue to different project silently clears parent

Added by Ewan Makepeace almost 13 years ago. Updated about 8 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Issues
Target version:
-
Start date:
2011-05-15
Due date:
% Done:

0%

Estimated time:
Resolution:
Affected version:

Description

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.


Related issues

Related to Redmine - Feature #5487: Allow subtasks to cross projectsClosedJean-Philippe Lang2010-05-09

Actions
Related to Redmine - Defect #6056: Bulk copying of issues does not preserve relationsClosed2010-08-06

Actions
Actions

Also available in: Atom PDF