Assign Issue to User without project access

[Felix Rucker]

Hi, 

we are a small company and recently started to work with jira. We are using next-gen projects, mainly because of the roadmap feature.

We want to assign certain issues to users which are not members of the specific project. This is possible in classical projects using permission schemes, I think. The next-gen projects now feature a way to configure roles within a project, which brings some of the permission scheme features through the back door. However, I can not restrict board access in the role definition which means, every user which is added to a project (regardless of their role) can access the board and view all issues (which is undesired). 

Is there any workaround? 

Thanks for any idea. 

Cheers, Felix

[Angélica Luz · Accepted solution]

Hello Felix,

Welcome to Atlassian Community!

On next-gen projects, there are not many permission settings. With that said, if a user has a license and needs to work on tickets, the permissions will allow them to view boards and other features, it's not possible to prevent that.

Currently, there is no workaround for that. For more details about next-gen permissions, please check the documentation below: 

• Next-gen permissions

If you have any other questions regarding this matter, please let us know.

Regards,
Angélica

[Christoph Jaenisch]

Hey, coming from Google...

For anyone who is interested how this works without issue security and also with next gen / Scrum projects: 

https://community.atlassian.com/t5/Jira-articles/How-to-allow-a-user-to-see-specific-tickets-w-o-issue-security/ba-p/870195

[Felix Rucker]

Hi Angélica, 

thanks for your reply. This is very unfortunate to hear. Is there any plan on when Issue Permission Schemes will be available on next-gen project? I would really help us to be able to assign issues to a licensed user without granting access to the whole board and with this to all tasks. 

Cheers, 

Felix

[Angélica Luz]

The permission scheme was already added, it's not the same as the classic projects because it's not a separate menu, but you can configure the permission for the role.

Also, on classic projects, there is no specific permission for boards, but it's possible to hide issues using the Issue security (also not available for next-gen).

[Felix Rucker]

Thanks for the clarification. I know that there is no specific permission for the board, however I think classical projects just allowed to assign issues to users outside a project, which is what I initially wanted to do. But that seems not to be a hot topic right now, so we will have to manage some other way. Thanks anyway.