nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

set security for parent issue so assignee of child issue can view the issue .

Umar Maroof

Hello everyone.

I am trying to set the issue security for an epic so that epic can be visible to the assignees of the child tasks under the epic.

and whenever the assignee changes for the task the new assignee now can be able to view the parent epic and the pervious assignee unable. How can I achieve this please help me in this.

Accepted answers

Trudy P Claspill

Hello @Umar Maroof

Are you working with issues in a Company Managed project or a Team Managed project?

If a Company Managed project, then per the Issue Security documentation

A security level's members may consist of:

Individual users

Groups

Project roles

Issue roles such as 'Reporter', 'Project Lead', and 'Current Assignee'

'Anyone' (eg. to allow anonymous access)

A (multi-)user or (multi-)group picker custom field.

There is no option to directly base the security level membership on information in a related issue.

I think you could work around this by

- having a multi-user picker field in the Epic

- using automation rule(s) to add/remove the Assignee of the Epic's child issues to the multi-user picker field of the Epic

- In the Security Level applied to the Epic, add the multi-user picker field.

I work with a Jira Free instance where I can't configure issue security schemes, so I have not had an opportunity to test out the above work around.

All comments

Trudy P Claspill

Hello @Umar Maroof

Are you working with issues in a Company Managed project or a Team Managed project?

If a Company Managed project, then per the Issue Security documentation

A security level's members may consist of:

Individual users

Groups

Project roles

Issue roles such as 'Reporter', 'Project Lead', and 'Current Assignee'

'Anyone' (eg. to allow anonymous access)

A (multi-)user or (multi-)group picker custom field.

There is no option to directly base the security level membership on information in a related issue.

I think you could work around this by

- having a multi-user picker field in the Epic

- using automation rule(s) to add/remove the Assignee of the Epic's child issues to the multi-user picker field of the Epic

- In the Security Level applied to the Epic, add the multi-user picker field.

I work with a Jira Free instance where I can't configure issue security schemes, so I have not had an opportunity to test out the above work around.

Umar Maroof

@Trudy P Claspill yeah exactly I am also thinking about the multiuser field idea for that in automation how pollute the assignees in multifield pickers ?

Trudy P Claspill

Here are three posts that talk about modifying a multi-user picker field.

https://community.atlassian.com/t5/Jira-Service-Management/Add-an-aditional-User-to-User-Picker-Multi-with-Automation/qaq-p/1554412

https://community.atlassian.com/t5/Jira-Software-questions/How-to-append-a-user-to-a-multi-select-user-field-in-Jira/qaq-p/1995845

https://community.atlassian.com/t5/Jira-questions/Automation-for-Jira-JSON-update-multi-user-picker/qaq-p/2185010

To add a user to such a field you are going to have to use the More Options option in the Edit Action, and add the users using JSON code.

The rule would need to be triggered by a change to the child issue Assignee field (Issue Field Updated trigger)

You would need to create a Branch/Related Issues/Epic (Parent) to "navigate up" to the Epic you want to modify.

Then you would put the Edit Action within that branch. To get the assignee from the child issue that triggered the rule you would need to reference {{triggerIssue...}} as mentioned in the first post I linked above.

The trickier part will be remove the Assignee that was removed from the child issue. To find that person you will have to look at the {{fieldChange}} object immediately after the trigger, and get the original value of the Assignee field.

Umar Maroof

@Trudy P Claspill I try to call assignee of the child but in below jason it call per user so what should I change so I can call the assignees of child?

{
  "update": {
    "customfield_xxxxx" : [
      {
        "add": {
          "accountId" : "yyyyy"
        }
      }
    ]
  }
}

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-software-cloud