How do I set up different security levels for different issue types in the project?

[Isabela Crepaldi Gonçalves]

I need help with the following:

I need to have 1 project, with multiple initiatives, epics inside of it, and Support tasks related. Support Team has its own board, but if Development starts working on one of their tickets, it should go to the development board. Support cannot have access to other development tickets, but they should be able to check their own tickets on the development board to check the status. I've thought about creating automation that sets security levels to Developers only for all the issue types that are not Support. Is there another, more efficient way? Is there someone in Jira that could help me with this?

Thank you.

[John Funk]

Hi Isabela,

When you say "Support cannot have access to other development tickets but they should be able to check their own tickets", do you mean an individual Support user associated with the ticket? If so, are they the Reporter? Or how is the association made to the ticket? 

[Isabela Crepaldi Gonçalves]

I mean the support team should not see any other ticket developers are working on except for the ones they reported - (the ticket Type is Support).

[John Funk]

Okay, I think I understand. I would create a Security Level called Non-Support or something like that. 

Then I would add the Project Role Developers to the security level along with the Project Role Administrators and Group Jira Administrators.

That way only people in those 3 project roles can see the ticket when the security level is attached to the ticket. 

I would then add an automation rule to set the Security Level to the name of your security level when an issue is created (Issue Created trigger) and with a condition where the issue type is not equal to Support.