Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Issue Type Security for Subtasks

I've just recognized, that Subtasks do not have the same Issue Type Security Level as the parent Issue. 
In my case, I have issues of type task and a issue type security set to reporter and assignee, works perfectly. I have a huge number of tasks which i assign to other guys. Those guys can only see issues they are assigned to or they have reported. 

Today the idea crossed my mind, to make subtasks to a parent task during a meeting. Now these guys cannot see the subtasks, but if a issue of type task is assigned to them they can access these tasks. 

1 answer

1 accepted

0 votes
Answer accepted
Sloan N_ B_ Community Leader Feb 03, 2022

Hi Hans-Joachim Fritz

One solution I can think of is to utilize Jira Automations to copy the Assignee and Reporter to the Subtasks as well as the issue security level.

The trigger might be the issue creation of all subtask issues in the relevant project(s) and the action edit using smart values with `{{.issue.parent}}`.

Look at this post by Atlassian: 

Sloan Niklas B.

I didn't implement any of your suggestions, but your explanation made me understand the problem. I've made the Issue in Mattermost and changed it to a Subtask in Jira. What I simply had not in mind, was that the subtask did not inherit the assignee automatically, so the assignee was still me.
My colleague clicked on the Issue in Mattermost and got the error message which sent me in the totally wrong direction.

Thanks a lot, Niklas

Sloan N_ B_ Community Leader Feb 07, 2022

Happy to help! It's great my suggestion brought you to the cause and a solution. :) 

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events