Users that are not part of a security level are still potential assignees - how can I prevent this?

Question

I have a project whose permission scheme is based on group membership.  Two subsets of users in this group have been set up into two different groups, each associated with a security level so that only the subset can create/work on issues at their level.  The problem is even with the level set the rest of the team still show up as possible assignees.  How can I limit assignment to only those at the security level?

David Willox · Answer

Hi Robert,

I stumbled upon another idea today that may be just what you are seaching for.

With a user picker field (unfortunately not the app default assignee field, but any custom user picker) you can customize the possible assignees by group  using the User filtering option. For example, if I set the filtering to a Lead or manager group then only those members are selectable. I can make the selection more robust by editing the field context and allowing this field to only be used in specific issue types. This would allow you to unify all the issues under one scheme but have different assignment levels for specific issues types. The solution would be pretty intensive as you'd need to create a new assignment field for each security level, tailoring the group filtering and applicable issue types to each field, but I believe that this would accomplish what you were describing.

Let me know if this helps.

Dave

Rob Horan · Answer

Scripting is not really an option for me at this time.  I'm not a programmer.

Rob Horan · Answer

Thanks Dave,

This is a bit absdurd/ridiculous to me as this circumvents the whole bloody point of issue level security in the first place.