issue level secuirty

[Scott McDonald]

Hello:

My project has 5 issue types. Am I able to set the issue level secuirty to one specific issue type or does the scheme inherently apply to all issues within the project?

Thank you, Scott

[Fidel Castro Armario]

Issue Security Schemes apply to all the issue types in a project.

You can use JIRA Workflow Toolbox post-functions to set different security levels to different issue types.

This is a simple example for automatically setting different issue security levels depending on issue types. We use "Set a field as a function of other fields" with the following configuration:

Setting rules in the example are:

(Bug)Public
(New Feature)Public
(Epic)Internal
(Story)Internal
(Risk)Management
(Purchase Order)Management

where Bug, New Feature, Story, Epic,... are issue types, and Public, Internal and Management are issue security levels.

[Scott McDonald]

When you say issue security levels, is this in the permission scheme or issue security scheme? Right now I have the issue security scheme limited to 2 user groups, however, when I add that scheme to the setting rules, it locks down all the issues where I'm only trying to use the issue security on one particular sub-task.

Here's what I have in my setting rules : (Stand Down - ADP Changes)ILM Changes

Here's a screenshot of my issue security level scheme:

Thank you,

Scott

[Fidel Castro Armario]

Issue Security Levels are defined in the Issue Security Scheme. An issue can be have security level associated, or none at all. If you set the security level in an issue, only the users that belongs to the groups or project roles associated to that security level, will be able to see the issue.

You can use "Set a field as a function of other fields" for setting security level only for certain issue types.

I assume that Stand Down - ADP Changes is the name of a issue type in your JIRA instance.

Please, attach a screenshot of your post-function's configuration.

[Scott McDonald]

Yes, Stand Down - ADP Changes is indeed an issue type. Attached are the screenshots you asked for.

[Fidel Castro Armario]

That post-function will set security level to ILM Changes, only for Stand Down - ADP Changes.

That issue type will only be visible to users in groups JIRA-ILM-Access and Dept-Internal IT.

[Scott McDonald]

The Stand Down - ADP Changes is a subtask so what you're saying is the way the post-function is configured, only the subtask should be 'locked' down but any other issues (parent and subtasks) will not be impacted by security level?

When I create an issue (parent) and try to view it, it states "This issue can't be viewed".

[Fidel Castro Armario]

Hi @scottjmcdonald,

It seems that subtasks share the security level with parent issue, so when you set security level of a subtasks, you are actually setting the security level of parent issue. There is an issue asking Attlasian to implement independent security levels for subtasks and parent issue JRASERVER-5869.

In the issue above there is a description of a workaround based on group picker custom fields, but I don't know whether it's valid for you.

[Scott McDonald]

Hi @Fidelcastro1612

I am going to take a look at the group picker option cause it looks like the security level on subtasks in a JIRA issue, not just the settings I have in my project.

Thank you, Scott