Restricting access to work types

[Luke Bradley]

I have a company managed implementation where work types represent a case, evidence items or a task. I want to be able to restrict access to these work types. For example, there are 3 projects, Cases, Evidence and Tasks. 

A case is a work type which will be allocated (assignee) to individuals, evidence work types and tasks are associated to the case work type by parent (case).

I want to restrict who has access to the primary level case and linked evidence items and tasks. 

Seeking ideas on the best way to implement this. 

[Trudy Claspill]

Hello @Luke Bradley 

Welcome to the Atlassian community.

Have you looked into the Issue Security feature?

https://support.atlassian.com/jira-cloud-administration/docs/configure-issue-security-schemes/

In what way do you want to restrict access? Do you want to prevent users from seeing the issues? Do you want to let the users see the issue but not edit it?

At what issue type hierarchy do the evidence and task item types exist?

[Luke Bradley]

For context, this is a software-project that has been designed into there separate Projects, named Cases, Evidence and Tasks.

The preference is to restrict all user from all 'Cases' (hierarchy 1) and then allocate each Case to selected individuals or people. 

Each Case with then have associated 'Evidence' and 'Tasks' linked by the Parent Case. 

Hierarchy:

Case - 1

Evidence - 0

Tasks - 0

So effectively any work issue (Case, Evidence, Tasks) that has been created and then allocate them to the elected individuals or people who are managing the Case. 

Any Evidence or Task associated with a case should also be automatically hidden from all.