Subtasks are not inheriting the security level of it's parent by default

[Eric Kanagy]

Hello-- We've setup security groups and are using them on an initiative. When I created an epic or subtask under the initiative, it defaults to no security group setting, instead of defaulting to the same security group as its parent (the expected behavior and what's noted in Jira documentation multiple places).

Is there a setting somewhere to change this? We need subtasks to default to the security group of their parents.

[Marc - Devoteam · Accepted solution]

Hio @Eric Kanagy 

If you use the parent field based on hierarchy, this is not considered a sub-task, but a parent child relation, this will not inherit the security level.

Question, are your sub-tasks created in the same project or another project?

If they are created in another project, there is no inheritance of the security level.

[Eric Kanagy]

Ok that's it! I'm creating Tasks on an Epic, (parent-child) so there's no security inheritance. When I create Subtasks on a Task, there is inheritance.

Thanks!

[Aaron Pavez _ServiceRocket_]

Hi @Eric Kanagy 

To better understand this can you send us:

- Screenshot of the hierarchy

- Screenshot of the security levels

I did a quick test and the sub task do get the security level of the parent.

Regards

[Eric Kanagy]

Here's the Confluence doc that clearly states: "Sub-tasks will also inherit the security level of their parent issue"

[Marc - Devoteam]

Hi @Eric Kanagy 

This document is based on on-prem installations, not the SaaS Cloud, but the same applies see:

configure-issue-security-schemes