Custimizing the Permission Scheme

[Elif Alverson]

Hello,

We have a project that the permissions are very limited for JIRA Users.

JIRA Users can create issues for this project however they cannot see the issue that they created.

I would like them to see the JIRA Issues that they created, but not the other issues for security reasons.  Is there a way to make this happen? 

Thanks!

[Nic Brough -Adaptavist-]

You have to give them a route to "browse project"

There are two ways to do this.

Create an issue security scheme that includes at least one security level and names "reporter" as someone who is in the level.  You then need to set the security level to be set on the issue automatically in post-functions or listeners, and once that is working, you can go into the permission scheme and allow all the users in to "browse projects".  They will then only be able to see issues that they reported (or are able to see because the security scheme allows them in a different way)

This is a bit messy and clunky, and does leave you with issues that users can change the security level on and remove it all.

I prefer the simple option of using "reporter browse" permission.  You have to change a config file and restart JIRA, and then educate your administrators to tell them you only use it for browse project, but it works perfectly, yo don't have to think about the workflow for security fields and you can't mess it up.

(p.s. you're going to ask why just putting "reporter" in the "browse project" doesn't work - it's because JIRA sees reporter as "anyone who might create an issue", so it'll give access to everyone who can create issues in the project!)

[Mario Günter]

Hi Elif, 

you could define security schemes / issue level security. You can refer to this official documentation here: 

https://confluence.atlassian.com/jira/configuring-issue-level-security-185729623.html

There you can add several levels and define which users / group will be able to see / edit issues and so on..

Cheers, Mario