In one of my JIRA project, I have 13 different security levels. Sometimes it is required to choose more than 1 security levels for a particular JIRA ticket but didn’t that option.
Well, we can create a separate security level with required user groups for the ticket but this is not an option as it will increase the number of security levels to infinite.
Many thanks an advance.
Thanks Jobin and Nic,
I am glad to have responses from two Atlassian Answer legends. :)
I am afraid, both project role and custom fields with multi-select will not work in my environment and tried both however security levels is the only option here and I am managing through it.
My question was a query and now it’s a wish. :)
Thanks again guys for your time.
That is the whole point of security levels. You add as many as you need :) But remember that you can have project roles and other types like custom fields which can be used in a security level. Maybe you can make use of them as well instead of just going with groups.
For example, you can use a custom field and then the issue owner can define who goes in that custom field value.
Thanks for your answer. This is exactly I am doing at the moment and its increasing my security levels from 13 to 14, 15, 16.......... but do you think this is a right option?
For example, I have levels like SL1 (Includes Group X) , SL 2 (Includes Group Y), SL 3 (Includes Group Z). Now if I want a JIRA ticket to be accessible only by X and Y, I have to create another levels which will include Group X and Group Y instead of selecting SL1 and SL2, but please think about the numbers of possible combinations when you have more security levels !!!!!!!!
The Security Level Fields needs to be multi select.
I don't think a multi-select works. Security levels are already complex, and in the real world, people don't think in multiple levels like that.
A typical scheme something like: top secret, secret, classified, restricted or unclassified. A document will have a single one of those stamps on it at any one time - it's utter nonesense to say something is "secret" and "restricted" at the same time - the higher level always trumps the lower one.
However... I suspect you are using security levels to model a group access system, which is quite painful. I think you should be looking more at roles to do this, and possibly moving to "security by group" model (Where you only have two security levels - public and restricted, and a group-picker on the issue, which is then used in the restricted security level)
I understand your point Nic, However situation is like this
I have 7 groups and has totally different users in it.
worst case scenario: I have to show ticket to 3 groups out 7 for xyz reason ( It could happen if I could use 3 groups in security level simultaneously)
And of course I do not want to create 8th group for those 3 together, otherwise I ll be creating groups forever.
How would you resolve it?
And I could if I knew the combination before hand.
So I created 7 checkboxes for each security group so user can check them as required (since security level gives single value select dropdown) and click on next step
and based on checkboxes I created filters for post function to add security level in that next step.
And It adds only one security group out of all the combinations.
I wish it could work in this way as mentioned. ( That's what clients want)
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
Hi, everyone! Molly here from the Jira Service Desk Product Marketing Team :). In the spirit of this month's august-challenge, we're sourcing stories of Jira Service Desk activation fro...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs