Issues security

[Alejandra Martin]

Hi people. Me again!!!! The reason of all my question is that i've working designing with Jira a way to resolve request for vacations. I think through automations can make all that our organization requires

But now, appointing to a security of issues I have following question.

Project 1

3 person reporters and 1 person approver

Is possible that each one of person can create its request and the other 2 reporters not see that request? But approver can view the request of the 3 reporters?

The 3 reporters nees to use all the issue type defined in project (Vacation, Study, Sick, Personal)

I'm searching trough Permission Scheme, Issue Security Scheme, but its not clear for me the behaviour.

The another idea to separate security , is make one project by person that contains the person, and approver.

Thanks in advance!

Alejandra

[Marc - Devoteam]

Hi @Alejandra Martin 

Create an issue security scheme, add 3 security levels.

Assign a level to a single user, and assign the approver to all 3 levels.

Have an automation rule in place that on issue creation checks who the reporter is and sets the correct security level.

https://support.atlassian.com/jira-cloud-administration/docs/configure-issue-security-schemes/ 

[Alejandra Martin]

Thanks Marc. I create the following

Its not clear for me how to continue. 

Thanks
Alejandra

[Marc - Devoteam]

Hi @Alejandra Martin 

Did you mean to add a screenshot, as this is not showing.

[Oliver Siebenmarck _Polymetis Apps_]

Hi @Alejandra Martin ,

You're actually already looking at the solution, it's Issue Security Levels (or Work Item Security Levels).

The way to set things up, is to have a security level for these requests, let's say you call it "Closed". You can then manage who can access work items with that level set. Jira does actually give you a lot of options here, including "Reporter":

So all you need to do is to allow access to the Reporter of an issue and to the approver. That could be an individual user or a project role or by group or whatever works in your case.

Hope that helps,

 Oliver

[Marc - Devoteam]

.