Jira Security levels malfuncion when i add a custom group select

[Nicolás Ferreira Neira]

Basically the title.

I have 3 security levels: user1, user2, user3

Each have 3 security permissions: jira admin, the user itself, and a custom group select.

Well, adding that custom group select broke security levels, as i want to create an issue with one of them, i see all security levels in the creation screen to pick

Any solution? is this expected?

Im on Jira Server 7.12

[Nic Brough -Adaptavist-]

If it is offering a security level to select, then you have "set security" permission, and you are a member of each level you see.

[Nicolás Ferreira Neira]

Maybe i wasnt explaining this right. 

I have 3 security levels named:

User 1

User 2

User 3

Inside User 1 there is 2 security permissions:

Jira administrators (group permission) 

User1 (single user permission)

The same with the other levels (user2 in User 2 level and user3 in User 3) 

When im log with one of these users i only see one security level in creation page. Perfect. 

Then, i want to add a custom field group picker to each one (empty, the idea is that this field would be fill in a later point in the issue), when i did this, in the creation screen i see the three security levels (User 1,User 2 and User 3). 

Why is that? I still want to each User only see their own security level, and only pick that one. 

Thanks a lot Nic! 

[Nic Brough -Adaptavist-]

That's because you are able to select a group that you are in, so you might be part of the security level.

[Nicolás Ferreira Neira]

Wow, didnt expect that. 

Is there any way to turn around that? 

I want to each one only see their security level, what is the point of this custom field value? 

Thanks for your time

[Nic Brough -Adaptavist-]

The custom field value allows you to define security levels by a selected user or group on the issue.

If your user selects a security level limited by a group or user-picker, then that issue will only be visible to that group or user, plus the others defined in the level.

Before the level is set, Jira cannot know whether a user might be selected by the custom field, so it has to assume the security level could be any of them.

[Nicolás Ferreira Neira]

Im sorry, but i think this behaviour make the whole group custom field value useless in security levels.

What if (like us) have 1000+ security levels? i have to surf and search for my security level?

There is not really a workaround this issue?

[Nic Brough -Adaptavist-]

Sorry, what issue?  The system is offering you what you have asked it to - the ability to secure an issue based on group membership.

I'd say if you think you want more than a handful of security levels, you're doing something wrong and should re-think what you're using it for.  Why would you have thousands of levels?