Having a story (assignee) populate an epic parent (staheolders - custom field)

[philipf]

Cloud server.

Looking for a solution:

I have a legal holds board. Which contains an epic with the legal hold documentation, and then each story (ticket type) is a legal hold custodian.

The user has to go into their ticket and switch status to acknowledge the legal hold.

This works great.

---

What I need is for users to only see where they are assigned to. And this I can do with a security scheme setting, and that works.  However, the users can only see their tickets that they are assigned to and not the parent epic ticket. 

What I need is for those users to see the parent ticket so they can access the legal hold documentation.

I thought to create a rule to take the assignee from the story level ticket and then populate a custom field in epic called stakeholders, and would then give those people permission to view epics tickets they are in the ticket of? But I don't see how I can get jira to do that. 

[Angélica Luz · Accepted solution]

Hi Alexandra,

Currently, Jira Cloud does not have the Nested Group feature.
We had a feature request suggesting this, but it was closed as "Won't do".
- https://jira.atlassian.com/browse/ID-167
For now, there are no plans to implement this.

If you have any other question, please let us know.

Regards,
Angélica

[Alexandra Smith]

While that is extremely disappointing, I do appreciate the quick and definitive response. Thanks.

[Angélica Luz]

You are always welcome Alexandra!

Regards,
Angélica

[Arnd Layer]

Nested groups does dramatically reduce the need to manage individual group memberships and therefore reduces the probability of errors. From my point of view, this decision makes the Atlassian Cloud less secure.

[Chris Power]

I agree this is really disappointing.  As our team size grows it's getting harder to manage group memberships.  This is such a standard concept for group/role management and it's available in the datacenter version.  I'd love to know why it was closed as "Won't do".

[Mariam Ahmadi]

agreed!

[Jörg]

Hi Angélica,

we are currently setting up our permissions and as we plan to grow users in the near future to a bigger scale I get asked why nested groups are not supported. While looking for solutions I only find links to the canceled feature request and explanation how to flatten the groups. 
But what I am really missing is an explanation why Atlassian Cloud is not supporting nested groups.

Best regards

joerg

[Deleted user]

Guys with a more complex setup of groups, the missing option of "nested groups" in the cloud is really painful.... Maybe reconsider your decision? or is there a reason we as customers don't see? what is atlassian suggestions to manage the groups?

[Luke Murphy]

I agree entirely

[Mariam Ahmadi]

What a bummer 

[krister.plahn]

10 years later and still not implemented.