Is it possible to restrict issue access based on a value in a custom field?

James Porter3

Hi,

I've created a custom field called Company, which is populated with our client company name's. Basically I am looking to give some form of read only access to my clients, but they should only be able to see issues that relate to their company only. So i am wondering if I can restrict access to issues in a project based on the value in the company custom field?

Thanks

Nic Brough -Adaptavist-

Sort of, but not really.

There are a few ways to approach restricting individual issues (e.g. using "only the person who raised this issue can see it") but what you really need here is "issue security"

This enables a "security level" that you can set on an issue. If it's blank, then just the project "who can browse" determines visibility, but if you set it to another level, you get to define rules. The more simple rules might be "Top Secret can only be seen by group X", or "Confidential can only be seen by people in the role of Y, and people in group X"

At that level, you'd have some pain, because you'd have to set up a security level for each value in the company custom field.

But... Security levels include rules like "is in custom field", which could solve this for you - you'd only need two security levels - "public (empty value)" and "private (determined by your field)".

That only works for select lists though, and if your company field is text, you'll need a different approach - set up the security levels, then write logic to read the company field and set the security level in a listener.