Issue Security Scheme - not securing anything
Asked by philipf:

In Jira cloud:

1. I set an issue security scheme

2. Made it default

3. applied to project

Everyone can still see every ticket? I thought this was suppose to limit the tickets that people can see.

Note:

1. In this board I have two ticket types which both should use the scheme (since default I thought this would happen anyways).![screencapture-convergemarketing-atlassian-net-secure-admin-EditIssueSecurities-default-jspa-2024-06-25-14_45_29.png](/t5/image/serverpage/image-id/331720i8004158B3551AE2A/image-size/large?v=v2&px=999 "screencapture-convergemarketing-atlassian-net-secure-admin-EditIssueSecurities-default-jspa-2024-06-25-14_45_29.png")


Answers:
author: philipf
body: This is the answer:  

It is all about the field 'security level' being added to the screens

What I did, if any help to anyone else was:

1. Created an approval board, and only wanted people who submitted issues and the people on the approval chain to see the ticket  
2. Two custom work flows for each ticket type, where when one is finished it creates the next ticket and carries over the fields (which all need security)  
3. Then have 4 custom fields, which are required when move to second status, since status one is a 'to-do', however still only want the reporter to see their ticket then  
4. So created a issue security scheme, where the people in each custom field (which are also used for transitions and post work), admin group, and finance group can see them.  
5. created an automation for when new tickets were created to set security level.  
It kept failing, I was stuck, nothing would work, everyone could see all tickets  
I then saw a video(<https://www.youtube.com/watch?v=qbS5COrug0E>) to add the security level field to the screens...and that did the trick. I can even go back and lock-down existing tickets.

<br />

<br />


author: Mikael Sandberg
body: Did these issues exist before you applied the issue security scheme? Existing issues are not affected if you apply a new security scheme and setting a level as default, that only applies to new issues. For the existing ones you can do a bulk update and set the security level.

comments: author: philipf
body: I have been creating new tickets to test out if it would work.  

I have also now tried changing the actor from automate to myself, both who have permission in the applied scheme to edit issues and update secuity schemes.  

![Screenshot 2024-06-25 154140.png](https://community.atlassian.com/t5/image/serverpage/image-id/331727i3DE251842E4C4F65/image-size/large?v=v2&px=999 "Screenshot 2024-06-25 154140.png")


author: philipf
body: It is all about the field 'security level'

What I did, if any help to anyone else was:

1. Created an approval board, and only wanted people who submitted issues and the people on the approval chain to see the ticket  
2. Two custom work flows for each ticket type, where when one is finished it creates the next ticket and carries over the fields (which all need security)  
3. Then have 4 custom fields, which are required when move to second status, since status one is a 'to-do', however still only want the reporter to see their ticket then  
4. So created a issue security scheme, where the people in each custom field (which are also used for transitions and post work), admin group, and finance group can see them.  
5. created an automation for when new tickets were created to set security level.  
It kept failing, I was stuck, nothing would work, everyone could see all tickets  
I then saw a video(<https://www.youtube.com/watch?v=qbS5COrug0E>) to add the security level field...and that did the trick. I can even go back and lock-down existing tickets.


Tags: cloud

jira-cloud