How can we configure a partner and ISV access in Jira software without using JSM

Question

Hi Team,

Does anyone have configure there Jira instance to provide the access to the Jira project where partners or ISV can able to create and access the issues they created but does not able to access the other issues from the project, also if there are more than 1 partner or ISV who need to access to the project how can we configure the Jira project using (Issue security, Project Roles, Groups, User picker field, group picker fields) so that partner or ISV can only access issues which are created by their team and not by other partner teams or ISV

We are not using JSM and want to configure the same in Jira software,

Thanks

Sagar

Elena Lurye_iyt0gr · Answer

Hi @Sagar Mahajan ,

Apologies for a delay, as I just noticed your message.

You can setup a security scheme with the default level that will consist of project role (call it "Partners", for example), and apply this security scheme to all your projects.

Then, on a project level, add required people to this role.

This way all the Partners XYZ in project XYZ don't need to have permissions to set security level (as it has only one level and it is a default level). Partners ABC will not have access to view issues in project XYZ, but will be able to see issue in project ABC, where they would belong to a corresponding role.

Hope this will work out for you!

Sagar Mahajan_d8sqh7 · Answer

Thanks for the reply @Elena Lurye any way we can automate the issue creation by one partner will set security level which that partner or partner team can view and other partners will not able to see that as I don't want to set it manually and also don't want to give partner a set security level permission.

for example xyz is a partner then security level xyz will apply to those issues when any team member create ticket in that project.

Elena Lurye_iyt0gr · Answer

You can use issue security with multiple levels - one for submitter, and another one (or more than one) for a user or/and a group picker field(s) on the issue (to have them involved as well)