Subtask security level

[Ángela Alcoba]

I need to put a security level to a subtask, which is different from the parent, but indicates that the security is inherited ... There is no way I can modify this? Greetings. Angela

[Nic Brough -Adaptavist- · Accepted solution]

No, the sub-tasks are there as a part of the parent issue.  So they need to take the same security level, as they're a tightly-coupled fragment of the issue.

[MattS]

I could see wanting a restricted sub-task. But a restricted parent would mean sub-tasks floating around with no parent for some users. Which would be odd. The workaround is to use a different issue.

[Ángela Alcoba]

Nic and Matt 

Thank you very much for the answers! We solve it by creating another type of task, as you say.

regards, Angela

[Carlos David]

Note that subtasks do *NOT* necessarily inherit the security level of the parent IF created via code/REST.

[Nic Brough -Adaptavist-]

Rubbish.  They do.

[Carlos David]

I'm not the only one: https://community.atlassian.com/t5/Answers-Developer-Questions/Subtask-does-not-inherit-Issue-Security-Level-of-parent/qaq-p/502087

[Nic Brough -Adaptavist-]

Only if you're on a REALLY old version, where there is a bug.

[Carlos David]

correction - hiding the security level on a subtask in its field configuration removes the security level entirely (it does not inherit).

[Agate Elīza]

Vote for the suggestion - https://jira.atlassian.com/browse/JRASERVER-65857