We have a Team in our organization that has a use case for managing permissions at a sub-project level (the term sub-project is being used loosely here - for their purposes it could be a component or a version, etc.).

Supposing there are user bases UB1 and UB2 (a set of users/groups/project roles), and sub-projects SB1 and SB2, and a hypothetical mapping that we have such that UB1 maps to SB1 and UB2 maps to SB2 - is it possible for us to set up permissions at the sub-project level such that users in UB1 would only see issues that correspond to SB1 and users in UB2 only see issues that correspond to SB2?

We would then want to extrapolate this such that one user base could map to multiple sub-projects and one sub-project could be accessible (i.e., the issues that correspond to the sub-project would be accessible) to multiple user bases and so on.

We have investigated the possibility of achieving this by using issue-level security in conjunction with JJUPIN scripts and have found that too complex and hard to maintain, especially with respect to scale. We have also investigated the Issue Type Filter plugin, but found that it does not suit our purposes since our objective is not to limit a user base to a particular issue type, rather to create any issue type, but limit other users from seeing the created issues.

Thus, we were wondering if JIRA offered any way for us to have permission management at a component (sub-project) level such that visibility/management of issues could be controlled at that level as opposed to at a Project level. Or would the official recommendation in this case be to just create separate Projects for each of our sub-projects?

Thank you.