Security level permission

[kiranmai c]

Hi, Iam trying to give security level permissions however facing challenges. I need to hide sub tasks to one group and have created a security level. I have an automation rule setup to create the Sub tasks automatically when a New Issue is created (Task/Story). For Parent I need security level permission - Level 1 and for Child I need Sec Level permission as Level 2. Currently the Security level for Child is being inherited from parent...however i tried to have one more manual trigger scheduled to update the sec level to Level 2 for all the Child Sub Tasks. But rule audit log shows successfully updated, when i check back the Sub task it would still shows the Sec level that its parent has.

Kindly suggest a solution. Iam using JIRA Cloud Standard Plan.

[Sebastian Krzewiński]

Hi @kiranmai c 

Ssub-tasks are a part of the parent issue. So they need to take the same security level, as they're parent.

I found ticket in Atlassian backlog but I don't know if Atlassian will do this in near future - https://jira.atlassian.com/browse/JRACLOUD-74883

Regards,

Seba

[kiranmai c]

Thank you Seba. It would be a great feature if they do it soon.

[Sebastian Krzewiński]

@kiranmai c please accept my answer if you think that my answer is enough. This will mark this question as closed and help other users to find a proper solution if they will have similar issue.