Permissions of project: Create issue ability but not restrict visibility of other issues and project

[Georgi Kostadinov]

Hello

I have project in Jira but currently cannot identify what options there are possible so I would ask for assistance from community.

Let me know if what I describe there are better ways for solving.

I would like that users (coming from AD) but are not explicitly added to my project are able to create new Issues to my project (And so edit their own created issues) but that other users are not able to see content of other issues (Different reporter then themself)

Is that possible and what capabilities I need in Project settings -> Permissions -?

Thank you in advance!

[Alysson Jhovert Malko de Freitas]

Hi Georgi,

You can achieve this using a custom Security Scheme for your projects, with a reporter security level (you can add the project lead or a group as well) :

And creating an automation rule for editing the Security Level after issue creation:

[Georgi Kostadinov]

@Alysson Jhovert Malko de Freitas 

I tried this but its not working

Can you explain more detailed your suggestion with custom issue scheme?

What means Reporter security level?

Do I need to assign any role to it?

How does it know it is for create ticket and view the specific ticket?

[carlosughini]

Hi Georgi,

Could you please provide us with more details about what exactly is not working?

By having this information we can help you to fix the issue.

Looking forward to hearing from you.

Cheers,

Carlos

[Georgi Kostadinov]

@carlosughini 

Thanks for reply.

There has been created new issue security scheme with reporter rule but when a user(jir-user role) try creating new issue, he cannot see the project.

So we add to "create issue ability" jira-user role and now the project is visible when creating new issue but the problem is that the user cannot see its own issues .

What I need as explained in other question is that a normal users (fx. jira-user role) can create new issues but are not able to see content of the project(other issues, or dashboard etc...) But they should be able to see their own issues and comment in them etc..

[carlosughini]

Hi Georgi,

What is happening is that, probably, the user is creating an issue that is with a security level that the user doesn't have access to.

First of all, you need to edit the project permissions and add all users that should be able to create issues with the permission Create Issue. You can, for example, create one group, add it to a specific project, let's call it "Users X", and add this project role to the permission Create Issue.

Additionally, you can set different security levels in the security scheme, and add the same group "Users X" to one security level, let's call it "Security X".

Important!

The users or groups that should be able to create the issues, should also have the permission Set Issue Security, so they can select the proper issue security level, otherwise, the ticket will receive the default security level that might be some that the users don't have access. I believe that this is what is happening in your case.

I strongly recommend checking the documentation below about issue security schemes:

• Configuring issue-level security 

Please give it a try and let me know how it goes.

Cheers,

Carlos

[Georgi Kostadinov]

@carlosughini 

This is working by your help.

So cool!!