-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Medium
-
Affects Version/s: 3.11
-
Component/s: Bulk Operations, Issue - Sub-Tasks
-
3.11
When doing a bulk move, Parent issues moved to a new project must take any subtasks with them.
If the new project has a different Issue Security scheme, then issues should get the default issue security in the new project.
Currently a bulk move will change the security setting of parent issues, but not of the subtasks.
- is related to
-
JRASERVER-10124 Editing parent issue security level is not reflected for sub-tasks when viewed in Issue Navigator
-
- Closed
-
- relates to
-
JRASERVER-10546 Moving a subtask doesn't inherit the security level of its new parent
-
- Closed
-
-
JRASERVER-11605 Moving a parent issue (with it's sub-tasks) that has a security level set into a project with no security scheme set makes the sub-tasks non-viewable in the new project due to retaining its original security level
-
- Closed
-