nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Security scheme current assignee on subtask but cannot view details on parent story

Nick Tymeson

We have implemented a security scheme where admins and contributors can view all issues. For other groups, they will only see issues they're assigned. This is controlled by specifying the 2 groups and "Current Assignee." in the security scheme level. Looks like if someone is assigned to a subtask, they cannot view the details in the parent story. Is there a workaround to enable people assigned at the subtask level to view the parent stories? With our setup, people are only assigned at the subtask level.

Accepted answers

All comments

John Funk

Hi Nick,

If you want them to see parent data, they will have to be given access to the parent. Or you will need to copy down data from the parent to the sub-task.

Nick Tymeson

Through the Add User/Group/Project Role to Issue Security Level interface, I don't see an option to natively give them access to the parent if they're assigned a subtask. Where would I do that?

John Funk

You would have to either add them as the assignee on the Parent or create a custom field to add them to and add that custom field to the Security Level and to the parent.

Nick Tymeson

I followed your suggestion with the custom field addition. I did the following:

1. Added a custom Group Picker field to the stories and epics.

2. Implemented an automation rule to automatically populate my custom field with the additional group I want to have visibility to the parent issues.

Then, I logged in as an outside resource and I still couldn't see the parent issue because of permissions. Any recommendations?

Ideally, there would be a custom field on the epics and stories, and the custom field would hold all people assigned to subtasks. Then, the security level will recognize all people in the subtasks and give them visibility to the epics and stories when applicable. By the looks of the options in the security configuration, this doesn't seem possible. Can you please confirm whether or not it would be possible on a per-user basis. Just because someone is assigned something in a group, it doesn't mean everyone in that group should have visibility.

Thank you.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud