[#JRA-13937] Bulk Move does not update the Security Level of subtasks

JIRA

Bulk Move does not update the Security Level of subtasks

Created: 11/Nov/07 09:22 PM Updated: 21/Nov/07 09:14 PM

Component/s:

Bulk Operations, Security, Sub-tasks

Affects Version/s:

3.11

Fix Version/s:

3.13

Time Tracking:

Original Estimate:

16 minutes

Remaining Estimate:

0 minutes

Time Spent:

4 days, 4 hours, 30 minutes

Issue Links:

Reference

This issue relates to:

~~JRA-10546~~ Moving a subtask doesn't inherit the security level of its new parent

~~JRA-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

This issue is related to:

~~JRA-10124~~ Editing parent issue security level is not reflected for sub-tasks when viewed in Issue Navigator

Participants:	Mark Lassau [Atlassian]
Since last comment:	40 weeks ago
Resolution Date:	21/Nov/07 09:14 PM
To be done by:	Pair of developers
Labels:

Description

« Hide

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.

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Mark Lassau [Atlassian] added a comment - 21/Nov/07 09:14 PM

This has now been fixed, such that the subtasks being moved inherit the security level from the parent issue objects in the parent bulkeditbean.