Issue security in Jira cloud

[serge calderara]

Dear all,

IN Jira DataCenter there is the possibility to give issue visibility to only certains groups base on Issue Security configuration and playing with Security Level field

In my customer cloud instance we have a set of ticket with a field name Source Operator, and we would like that users who belowgs only to SourceOperatorGroup can see those tickets only and not the others

Is tehre any way to do that in cloud ?

regards

[Kai Becker]

Hi @serge calderara 

thanks for your question. If you're in a company-managed project, the way of configuring the issue security is the same like it is on data center / server.

If you are using a team-managed project, it is not possible to use issue security.

The type of project you are in can be seen in the bottom left of the project.

Hope this helps 🙂

[Trudy Claspill]

Correction, in Team Managed projects there is an issue security function but it is implemented differently. It is called Issue Restrictions.

https://community.atlassian.com/t5/Jira-articles/Announcement-Control-access-to-your-issues-on-next-gen-using/ba-p/1430115

https://support.atlassian.com/jira-software-cloud/docs/set-up-issue-types-in-team-managed-projects/#Setupissuetypesinnextgenprojects-restrictIssueTypesRestrictaccesstoanissuetypeinyourteam-managedsoftwareproject

[Kai Becker]

Thanks for the correction @Trudy Claspill 🙏🏻

[Rilwan Ahmed]

Hi @serge calderara ,

By the use of Automation rule, you can achieve this. 

1. Go to project permissions, grant Automation user required permissions to set security level
2. Go to Project settings --> automation --> Create rule
   • Create Trigger == Issue created
   • Add Component --> IF: Add a condition --> Issue fields Condition
   • Select required field and value
   • Add Component --> Then: Add an Action --> Edit issue --> Select "Security Level" in fields dropdown and select the required value for it. 
   • Save and Publish the Rule.

Your rule should look like attached screenshot. here "Access Type" is a custom field

[Marc - Devoteam]

Hi @serge calderara 

This would require that you already have setup a Issue Security Scheme.

And if you use a Company Managed Project as mentioned by @Kai Becker 

[serge calderara]

@Marc - Devoteam thanks for the info.

I have define my security scheme with 2 values and groups
I have add the field in my Create/Edit screen
I have added myself in Set Security Lebel permission

Then when I create a sample ticket, I cannot see in my Security Level field the list of option I  have define in the sheme which is associate to my project, the list is simply empty

Any idea ?

[Marc - Devoteam]

Hi @serge calderara 

The Security Level is not visible as a field on an issue, if your scheme is enable on your project, in the top right corner of an issue a "lock" icon will be displayed, left of the watch option.

This is the security level field.

[serge calderara]

@Marc - Devoteam what I mean is that when I create an IT Serivice Management ticket for an issuetype, I have the field security level shown on my form but when I click on it its says "no options" BUT in fact the level has been created in the scheme associated to the project

I need to set that Secuity Level field, but why my option are not displayed in the list while I have full right to set it ?

Youc an see from below that I have created a scheme and associate it with a single value option EvPAss, but does not appears as an option in the list when creating the issue

Any idea how to solve ?

I have notice also, that if I open an existing issue type for which I have place the securty level on screen, I do not see the locker icon as you mention

regards

[Marc - Devoteam]

Hi @serge calderara 

The Security Level field can't be set by a customer on a request type in Cloud.

There is an open Bug at Atlassian for this.

https://jira.atlassian.com/browse/JSDCLOUD-4259

[serge calderara]

@Marc - Devoteam wierd :-(

What is the way I could set this field afterwards when issue request type is already created ?

possible with automation or the bug still applied ?

regards

[Marc - Devoteam]

Hi @serge calderara 

Yes you are able to set it with an automation rule.

[Rilwan Ahmed]

Hi @serge calderara ,

You can refer to my first comment on how to set security level through automation. 

[serge calderara]

@Rilwan Ahmed thnaks for your comment, this is exactly what I do but for some reason when I define the Edit issue and select the  field Security Level to be set, the in the drop down list, there is nothing displayed to be selected.

My scheme level option define are not shown in the field .

Even if I have full right to edit it

Any reason why I do not see my option defined ?

regards

[Marc - Devoteam]

Hi @serge calderara 

You need to add yourself to the security level as well.

Security levels do impact administrative rights as well.

So if you are org-admin, site-admin or jira-admin, if you start using Issue Security make sure that you add yourself or the relevant group for admins in the security level as well.

[serge calderara]

@Marc - Devoteam thnaks it works

I have one last question.

If the security Level is implemented at the Service Management project, does the tickets will be see from user which use the user portal and select All Request filter ?

What I mean is the following :

1. Let say USer1 create a request REQ1 from the portal
2. USer1 create request REQ1 from the portal
3. The security level in place says that USer1 and USer2 can only see theire own ticket from the project in Jira

Question : If USer1 select All Requet from the Request button at the portal level, does USer1 will be able to see ticket from USer2 ?

Regards

[Marc - Devoteam]

Hi @serge calderara 

They will just see their own issues