different security levels on a project

[Maktumhusain Taseeladar]

i'm trying to create different security levels on a project visible to the customer users. 1st group should be view only for them, the other should be edit, and a third group will be Amdocs only, not visible to the Customer at all. Security level is determined according to issue types and is assigned by automation. There are 3 security groups - 1. Customer Edit, 2. Customer View, 3. Amdocs users. The two customer groups contains same users- that might be the issue. In reality all is working issue types are getting the right security level but both the view and edit levels are enabling the customer to edit. there isn't really a 'View' only level for the customer. Customer can Edit anything. your ideas will be appreciated!

[John Funk]

Hi @Maktumhusain Taseeladar 

If the you are assigning the levels to groups and the groups have have the same people in them, then yes that's the problem. Each level will need different people assigned to them to have different results. Customers that should be able to edit need to be in a different group or project role, and then that group/project role used for the Customer Edit security level instead of the group that contains all customers.

[Nic Brough -Adaptavist-]

Security levels have nothing to do with anything that someone might do with an issue other than their ability to see them.

You need to be looking at the permissions in the project - they control the edit (and transition, and assign, and comment, and and and) abilities.

Security levels simply hide issues from people not defined as being in the level.