User rights Create ticket and see only own tickets - permission scheme

Question

Good morning,

I would like to configure the following in a Jira software project regarding user rights:

- Employee can create a ticket
- Employee is only allowed to view or edit the tickets he created within the project.
- Exception if a user is added as observer, he is also allowed to see these tickets additionally.
- Der Benutzer darf diese Tickets nur erstellen aber nicht im Workflow weiter ziehen

Is there any guidance or possibly best practice on how I should proceed to implement this?

Aurélien D'AQUINO · Answer

Hi there.

Were you able to check and make it work ?

I'm struggling with the same issue actually, and every time I almost get there, it bearks some other access (we have few groups like this with different levels like everyone can do anythin, everyone can see issues in project but not edit except few, everyone can create but see nothing apart from few, and finally the case here, everyone can create and should see only it's own tickets+watching ones)

If anyone at Atlassian is watching this thread, that would be a HUGE help to have a 1-click configuration for those "usual" cases, maybe an assistant to do it with few options at project creation would be saving tremendous admin time.

cDemmerle · Answer

Hi @Valerie Knapp ,

THX ! i will have a look on it and make a test.

After that i will respond here....

Greetings and a nice Weekend!

Valerie Knapp_dpp5c6 · Answer

Hi @cDemmerle , thanks for your question.

What you are describing to me could be implemented with an Issue Security Scheme.

Here is some documentation explaining how to set them up - Configure issue security schemes | Atlassian Support

How it works is that the scheme can be configured with an additional 'layer' if you like, of security. You can designate an issue security level as the default one so that, when a user who has the appropriate project permissions creates an issue, that the issue is assigned a security level that makes the issue viewable to them. However, for the next user, the same rule would apply, so two different users wouldn't necessarily be able to see each other's issues.

There are different use cases for this, for example, in a HR setting, where you can set different levels of permission so that only some users can see everything, and others can only see what they need to.

I would encourage you to read the documentation and see if this solution could work for you. If not, please give us your feedback and either myself or someone else can try to help.

Cheers