Issue type read permission for a dedicated group

[Beyer Gertrud]

Dear Comminity,

Please help me to define an issue type which can be seen just for a dedicateted group. We have no script runner add on, so I need to solve it without script runner.

In this project there are several issue types can be seen for all jira users, but this new issue type can be seen just for a dedicated group members.

Thank You very much!

Gertrud

[Trudy Claspill]

Hello @Beyer Gertrud 

Are you working with a Team Managed project or a Company Managed project? You can find that information in the Type column on the View All Projects page under the Projects menu.

If it is a Team Managed project you would use the Issue Security feature.

https://support.atlassian.com/jira-software-cloud/docs/set-up-issue-types-in-team-managed-projects/#Setupissuetypesinnextgenprojects-restrictIssueTypesRestrictaccesstoanissuetypeinyourteam-managedsoftwareproject

If it is a Company Managed project you would use the Issue Security Scheme feature.

https://support.atlassian.com/jira-cloud-administration/docs/configure-issue-security-schemes/

Before diving deeper into either of these processes, please let us know your project type.

[Beyer Gertrud]

Hello @Trudy Claspill 

Thank You, for your answer!

I'm working with a Company Managed project, but after I ask the Community, came a new ask for my company, so now my question changed.

I need to know, that how can I define permissions for a concrete issue . For example there is an issue, which can be seen just for a dedicated group.

Thank You very much!

Gertrud

[Trudy Claspill]

If you were going to need to secure multiple issues another solution could be to have those issues in a separate project and limit access to that project to the dedicated group.

If the issues that need to be restricted are in the same project as issues that do not need to be restricted, and that is a Company Managed project then the answer is Issue Security Schemes.

In an Issue Security Scheme you create Levels that identify who can see an issue assigned to that level. You then set the Security Level in the issues you want to secure. 

Whomever needs to be able to change the Security Level assigned to an issue needs the Security Level permission in the Permission Scheme associated with the project.

If an issue has no Security Level assigned then all user can see it.

I advise you to work out the details with a test project first.

[Beyer Gertrud]

Thank You very much!