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

[Hernan Halabi - Elite IT Consulting Group]

If I recall correctly, if you set a permission scheme with only the reporter on the create and browse project permission that achieves the same behavior than what was suggested by @Nic Brough -Adaptavist- 

even though it does the trick I believe it's better to use the security schemes that are meant for that 

[Nic Brough -Adaptavist-]

Ah, um, no, because when you say "only the reporter can create", you don't know who the reporter is until after creation, so Jira lets everyone report.

[Hernan Halabi - Elite IT Consulting Group]

Correct, I believe that's the intention here. Anyone can report but not anyone can see everything within the project. A role should be added on the browse project permission as well for that set of users that are meant to see all the project that I didn't mention on my reply.

[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"

[Sam Huawey]

@Nic Brough -Adaptavist-  no, it makes sense. E.g. someone creates a request about his salary in Accountants project. Only reporter and Accounter (role in the project) should be able to see it. Reporter does not need Browse projects permission to Create and he should not need it to browse his "own" issue and comment it if needed.

Edit issues permission has Reporter selection. Browse projects permission does not have it.

Maybe Atlassian should think about separating "View issues" from "Browse projects" permission. This will help in cases like this one.

[Nic Brough -Adaptavist-]

No, it does not make sense to separate "view issue in project" from "see project"

But Atlassian have given you the ability to implement it, as I wrote up.