Hi everybody, how can be ensured that a project's default security level is used for all issues in this project and never the "none" level? Context: * JIRA 5.0 * two JIRA projects PROJECT and SUPPORT, different security levels * SUPPORT has a restrictive default security level (every user sees only his own issues) Scenario: * Internal user browses PROJECT * he creates new issue, changes project from PROJECT to SUPPORT * user enters title and description and saves the issue Problem: * The created issue does not have the default security level and is publicly visible * security problem! Explanation: * when browsing PROJECT and creating an issue the default security level (none) is selected * when changing the project to SUPPORT all field values are maintained, also the security level So if an internal user does not explicitly set the security level a publicly visible issue is created. What possibilities are there to ensure that the default security level is always used in the SUPPORT project? Thanks!

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; } } }

Security level problem when creating JIRA Issue

NielsJ

Hi everybody,

how can be ensured that a project's default security level is used for all issues in this project and never the "none" level?

Context:

JIRA 5.0
two JIRA projects PROJECT and SUPPORT, different security levels
SUPPORT has a restrictive default security level (every user sees only his own issues)

Scenario:

Internal user browses PROJECT
he creates new issue, changes project from PROJECT to SUPPORT
user enters title and description and saves the issue

Problem:

The created issue does not have the default security level and is publicly visible
security problem!

Explanation:

when browsing PROJECT and creating an issue the default security level (none) is selected
when changing the project to SUPPORT all field values are maintained, also the security level

So if an internal user does not explicitly set the security level a publicly visible issue is created. What possibilities are there to ensure that the default security level is always used in the SUPPORT project?

Thanks!

Accepted answers

All comments

NielsJ

Exactly, the default security level gets not applied. But this is no bug (from my point of view) since it is a feature that field values are mainained when changing the project in the create issue dialog.

If there was a possibility to disable the none security level this would not be a valid value and the default security level (which would be then the only one) must be selected.

Vishwajeet Singh

I am not sure if I understand your question as it's kind of confusing to me, are you saying default security level which you set from configuration is not getting set ?

David Toussaint _Communardo_

Basically it gets applied, just only initially. Though, when the project changes (to a project that has a different devault level) the pre-set security level from the first project will stay and does not change to the default level of the "new" project. Kind of annoying!

Radu Dumitriu

It's a feature. We used this plugin to solve this kind of problems: https://marketplace.atlassian.com/plugins/com.keplerrominfo.jira.plugins.blitz-actions (i.e. create a button "Move SUPPORT", and scripted the creation of the issue,l setting the correct security level).

Renjith Pillai

Or create a new issue security scheme for the SUPPORT project with a default security level (and keep the security level names different, just to be sure). It will get applied when the issue is moved AFAIK.

NielsJ

I'll try that!

NielsJ

Another option if it is possible to change VM files: https://confluence.atlassian.com/display/JIRA/How+to+Remove+%27NONE%27+from+a+Select+List+Custom+Field

David Toussaint _Communardo_

Default values are set for both affected Security Schemes. Though one has set "none" as default (whcih is also present in the other one, just not default) and as soon as we switch the project the security scheme gets NOT changed (as "none" is available in both shemes, but onle the default value in one scheme).

So that looks just as it is set up right now...

Welcome!

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

Quick Links

Find more posts tagged with

jira