Create an issue without browse permission

Joseph Hani

Hello everyone, 😁

I have a project I'm working on, on Jira Software Cloud, where I created the Permission Scheme so that only a limited number of people have the Browse Permission.

However, I would like a user who does not have the Browse project permission, to be able to create an issue. Is this already possible at this level? 

The dilemma I have is that I want the user to be able to see only the tickets and update that he has created inside the project where he does not have Browse permission. And TADAM, this is where it gets tricky and could not find information. 

If anyone has any information, I would be very grateful.

Have a nice day everyone 😊,
JH

 

Nic Brough -Adaptavist-

Your requirement directly contradicts itself when you say "... a user who does not have the Browse project permission ... user to be able to see only the tickets and update that he has created"

Do you want them to be able to see the issue or not?

I'm going to assume that you do want them to be able to see the issue. 

The starting point for this is to understand that if you cannot see a project, you can't do anything with it.  But there are ways to work with issues that enable you to get "only able to see my own issues"

• Set up the project permissions so that people can do whatever you want them to be able to do with the issues in the project, ignoring the "only my issues" bit.  Set the permissions for people who need to create, edit, comment, transition and so on, as though there were no restrictions.  For a simple working example, let's say you say "Create: role: users" and "Edit: role: users".  Whatever permissions you grant, you must include "set issue security: (same as the 'create' rule)" 
• Create an issue security scheme for the project with one security level that has a simple rule of "role: reporter"
• Default the security level to the level you've created.

You now have a project where only the people who report an issue can see the issues they reported.  This is probably totally useless to you (unless it is a "private to do list" project), so you probably want to add other people to the security level - in my example, maybe "role: developers"