Component and versions permissions

[James Wardle]

Hi,

We currently have a Jira project created that has numerous components underneath, and each component has a separate team of developers/QAs working on it. This project also has versions relating to each component e.g. Component 1 will have version 1, Component 2 will have version 2 etc.

Currently all the teams with access to the project can see all the components and versions, and over time this will expand, so may get confusing. 

My question is:

Is it possible to restrict access/visibility of the components and versions so that a team can only see the components/versions relevant to them?

Thanks

[Krister Broman _Advania_]

Liming the ability to view an issue is called issue permissions. It is not possible to set this based on the component and versions, however it is possible to do it based on a group or user custom field. 

So if you were to use automation to set a group custom field then you could set rules like when Version 1 set Group 1 or when Component 2 set Group 2 etc. 

Then you could use issue permissions to limit so that only the group listed in the group field would be able to see the issue.   

[James Wardle]

Thank you for the reply. I'll give this a try and will let you know how I get on.

[James Wardle]

If I follow the method above, will it allow me to limit the visibility of the available versions in the Versions panel? e.g. Version Component 1 visible only to the group in the custom group field. I'm guessing not but thought I'd ask.

[Krister Broman _Advania_]

No it would not limit the versions you see, Issue Permissions are only a way to limit the view of the issue in full. If you see versions in the issue you will see all versions related to the project.

[James Wardle]

Thank you for the reply.