how can be ensured that a project's default security level is used for all issues in this project and never the "none" 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?
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.
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!
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).
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...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot