Set permissions on specific projects (Company Managed projects)

[Anders Hebert]

We use Company Managed Jira-projects in our organisation. I have been asked to create a new Jira-project, for a management team - who do not wish for their Jira-project (or more  precisely issues) to be accessed by all employees. What would be the best way of solving this? I have so far only managed to think of two possible options:

1) Create a Team Managed Jira-project, where this is easy to do. However, I would like to stick with our organisational standard of using Company Managed jira-project as much as possible.

2) Create a Company Managed Jira-project and use a specific Permission Screen for this project? Something I have never tried (if so, what are the steps for doing this?)

Are there any other options, that are relatively simple?

We are using Jira-Software Premium (Cloud)

[Marc - Devoteam · Accepted solution]

Hi @Anders Hebert 

I would use option 2.

Via the issues section in Jira Administration (cog wheel), choose the Issues option and then select Permission Schemes.

Create a new scheme, set the required permission to the jira group containing the MT members.

Als o see the documentation here; Create-a-permission-scheme 

[Debbie Jolley · Accepted solution]

I would 100% recommend sticking with a company-managed project. 

Copy your generic permission scheme to make an individual scheme specific to this project.  Set up a Group for the management team that you wish to access the project.

Then the only permission you need to change from you normal one is the Browse Project permission - remove 'all logged in users' (assuming you generally use a default) and replace with the Group you have just set up for the management team.

You don't need to change anything else in the Permission scheme as Browse Project acts as a kind of gatekeeper to the project.

[GNarsimhagowda - Empyra]

Hi @Anders Hebert  ,

Is there any way you can implement "issue security" for your need! . 

for reference : Issue Level security

This way others will not be able to view the ticket unsless they have issue security configured.

Thanks.

[Marc - Devoteam]

Hi @GNarsimhagowda - Empyra 

This can work of course, but the question is relating a new project.

Not modifying anything to existing projects, so permission scheme rules over issue security as that's just on issues within a project.

[John Funk]

Hi Anders,

Either way, you are looking at implementing permissions. Doesn't matter if you have a Team-managed or Company-managed project as it relates to that. So, the question is what else does the project need? Team-managed projects are very limiting but control rests with the project admin, who is usually not real Jira savvy either.