Issue Security Levels from Epic to task

[Yana Baklaikina]

Hi everyone,

I’m trying to configure Issue Security Levels in Jira Cliud and would appreciate your advice.

My goal is to achieve the following setup:

• The Epic and all its child issues (Tasks/Sub-tasks in the hierarchy below) should be visible to the Supervisor.

• Each individual Task should be visible only to:

  • the Supervisor (of the task and supervisor of the epic), and

  • the specific Assignee of that task.

• Assignees should only see their own tasks, not tasks assigned to other team members.

• However, the Supervisor should see everything within the Epic hierarchy.

Is this possible using standard Issue Security Levels?
If so, what would be the best way to configure this, especially considering the hierarchy under the Epic?

Thank you in advance!

[Marc -Devoteam-]

Hi @Yana Baklaikina 

Create an issue security scheme with a 2 levels, on 1 level add project role Supervisor and Current Assignee.

On the other level (2) only add the project roleSupervisors.

The catch here is that the Epic work type should use a different workflow then the Task and Sub-task work type.

Then in the workflow on the creation action (in both work flows) add a post-function to set the security level.

So in the Epic workflow, set the defined level 2 (other) and in the workflow used for the other work types, set the level on level 1.

Use the ootb post-function; Set issue security level based on user's project role

[Ravi Sagar _Sparxsys_]

@Yana Baklaikina 

The security level cannot on its own be inherited to child issues. As @Marc -Devoteam- mentioned you can create post function to set the default security levels based on assignee, reporter, group or may be a value from the user picker field.

Automation rule can potentially be used here to set the security levels for Epic and its child issues.