Hello Checking for tips on the best way to complete Issues Security process. I have completed the following steps however trying to understand how to tie the newly created Issues Security to an Issues Type. * Created Issue Security Schemes * Created Issues Security level for: General Userbase (All users) * Created Issues Security level for: Overview * Create Group for Overview via HESD Portal Settings and Portal Groups. * Added one Issue Security Scheme to Jira Service mgmt. Center project * Tie Overview Issue Type to Overview Security level. I have read a few resources and its not clear on next steps. Thank you

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Tie Issue Type to Security level.

lapacquah.bryant

Hello

Checking for tips on the best way to complete Issues Security process. I have completed the following steps however trying to understand how to tie the newly created Issues Security to an Issues Type.

Created Issue Security Schemes
Created Issues Security level for: General Userbase (All users)
Created Issues Security level for: Overview
Create Group for Overview via HESD Portal Settings and Portal Groups.
Added one Issue Security Scheme to Jira Service mgmt. Center project
Tie Overview Issue Type to Overview Security level.

I have read a few resources and its not clear on next steps.

Thank you

Accepted answers

Nic Brough -Adaptavist-

I think there may be a bit of misreading happening here.

You've said, "tie issue type to security level". Jira does security levels at the project level, not the issue type. All issues within a project have the same security-level options.

If you want to tie an issue type to a security level, you need to automate some rules that tie them together somehow.

All comments

Mikael Sandberg

You can do this with automation. Just create a rule that sets the security level when an issue is created and is of the specific type.

Brant Schroeder

@lapacquah_bryant Issue Security is applied to the issue type or request type when it is created. You do by setting the default issue security as explained here: https://support.atlassian.com/jira-cloud-administration/docs/configure-issue-security-schemes/

Set the default security level for an issue security scheme

You now have the power to select the default security level that will be applied to issues assigned to each security scheme. Some things to keep in mind when setting a default security level:

If the reporter of an issue does not have the 'Set Issue Security' permission, the issue will be set to the default security level.
If an issue security scheme doesn't have a default security level, issue security levels will be set to 'None' (anyone can see the issues).

Select > Issues.
Under ISSUE ATTRIBUTES, select Issue security schemes.
Click the scheme name or the Security Levels link in the Actions column.
1. To set the default security level, locate the appropriate Security Level and click Default in the Actions column.
2. To remove the default security level, click Change default security level to "None" link (near the top of the page).

lapacquah.bryant

I have created this before and just missed this last step and I did not have to create automation rule nor set as default. The issue type is in a project with other users and there is already a Default security level selected. However I have a user who does not want others within project to view the request submitted.

lapacquah.bryant

Brant Schroeder

@lapacquah_bryant Once you apply the scheme to your project you still need to dictate how that is applied to each issue type. If you do not apply it by default or through automation or through the workflow (an additional option) or by exposing the security level on the issue screen so the user could select it at creation (additional option) then it would not have been applied. You would have had to do one of the four options.

Nic Brough -Adaptavist-

I think there may be a bit of misreading happening here.

You've said, "tie issue type to security level". Jira does security levels at the project level, not the issue type. All issues within a project have the same security-level options.

If you want to tie an issue type to a security level, you need to automate some rules that tie them together somehow.

Joseph Chung Yin

@lapacquah_bryant -

Just as other community leaders stated which I agreed with them, you can still apply your new security level manually via the "Security Level" field for each issue. Therefore, those issues will only be visible if the assigned security level call-out the specific users within a project.

Not quite understanding your statement of "I did not have to create automation rule nor set as default"? This is why I suggested above that one (if he/she has the "Set issue security" permission against the project - This is defined in project's permission scheme in used) can thus still manually change the security level manually issue by issue to lockdown the issue visibility and access.

Hope this helps.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Technology Applications Team

Viasat Inc.

lapacquah.bryant

Thank you for the update, this is a new process so there are no associated Issues at the moment.

lapacquah.bryant

Thank you can I get tips on Automation rule please. I am not seeing anything related to setting security level when issue is created.

lapacquah.bryant

I found an Automation rule that works. Thank you

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management