How to set a security level on sub-tasks?

Yousif Al Rawahi April 1, 2024

When the main issue is created, 6 sub-tasks will be created automatically by automation. I want to set security level of each sub-task, how to set a security level of each sub-tasks by automation?

3 answers

1 vote
Armitha Reddy Toorpu Ceema April 1, 2024

Hi Yousif,

 

Go to Rule details.

Under "Rule Details," try checking the checkbox and then try again.

Please check the checkbox as shown in the screenshot below.

Screenshot (268).png

 

Thanks,

Armitha.

Yousif Al Rawahi April 1, 2024

I have checked the box and it still the same thing. I guess the security level won't apply for sub-tasks only without the parent issue right?

Armitha Reddy Toorpu Ceema April 1, 2024

Yes, security level won't apply for sub-tasks only.

 

 

0 votes
Sreenivasaraju P
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
April 1, 2024

Hi @Yousif Al Rawahi ,

 

As per my knowledge, Subtasks inherit the security level of their parent issue. We can't have two different securities. 

 

There is an open suggestion with Atlassian for the same. 

https://jira.atlassian.com/browse/JRACLOUD-74883

Yousif Al Rawahi April 1, 2024

Is there a way to apply a security on sub-tasks other than security level, for example scriptrunner?

0 votes
Armitha Reddy Toorpu Ceema April 1, 2024

Hi Yousif,

 

Below is the automation for to set Issue security level for sub-tasks.

First you want to create Issue security scheme and create security levels under that scheme.

Please do adjust the trigger and condition based upon your requirement.

Screenshot (267).png

Please accept the answer if this helpful for you.

 

NOTE:- This suggested answer will work for Jira cloud. 

 

Thanks,

Armitha.

Yousif Al Rawahi April 1, 2024

When I used issue created trigger, it says 'no actions performed', and the reason is that 'The following issues did not match the condition', but when I use 'issue transitioned', it works. But I want the trigger as 'issue created'. What could be the problem?

Btw, when I used 'issue transitioned' trigger', it automation worked successfully but nothing happened when I checked the sub-task.
Screenshot 2024-04-01 132045.png

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events