How can "Hierarchical" access permissions can be accomplished in JIRA projects?

[Tuan Duong]

A project has components C1, C2, C3.... We have three groups of users.  {X, Y, Z}.  Users in group X should have access to all issues for C1, C2, C3....  Group Y should only  have access to issues for C1, C2, and Group Z should only have access to issues for C3

Is there a way to achieve this objective in JIRA

[Joe Pitt]

The only reasonable option is to have 3 projects, one for each issue type and give the users access to those projects as needed. 

[Nic Brough -Adaptavist-]

To answer the question literally:  Rewrite Jira and add the code required to do permissions at lower levels.

Jira permissions are done only at a project level.  There's nothing to cascade down to.

You can do a little bit with issue security, but that only applies with "view", not the other 25ish permissions.

To do what you describe, you will need two things:

• An issue security scheme with levels for each group saying "only that group can see issues in this level"
• A listener that reads the components and sets the level appropriately