Permits for secured projects

[Marcos Pino Flores]

I have a visibility issue in Jira: Project A is highly secured, allowing access only to its members, while from Project B I clone issues to Project A, thus linking them both; however, Project B users cannot see the cloned issues or access Project A due to their security settings, so I need to know if there is a way for these users to see only the cloned ticket in Project A, or at least a specific board related to those cloned issues, without granting them full access to the entire Project A.

[Trudy Claspill]

Hello @Marcos Pino Flores 

Welcome to the Atlassian community.

What are the Types of these projects? Get that information from the Types column on the View All Projects page under the Projects menu.

Generally speaking, a user must have the Browse permission (in Company Managed projects) to see any of the issues in the project. Which issues they can see in a Company Managed project can be further restricted by using an Issue Security Scheme and Security Levels.

https://support.atlassian.com/jira-cloud-administration/docs/configure-issue-security-schemes/

Team Managed projects have a different way of managing access, visibility, and issue security. If one or the other project is Team Managed, let us know and we can delve into that topic.

[Fabian Lim]

Hi @Marcos Pino Flores

Welcome to the community!

In summary a Field configuration scheme would do it for you.  Link: https://support.atlassian.com/jira-cloud-administration/docs/manage-issue-field-configurations/

You would need to create a field configuration for Project A and have a user custom field that allows the users on ticket B to see the specific ticket in Project A.  This has to be populated via the automation and/or manually.  You will also need to give them "browse" access to Project A.  But it's the field configuration which will grant permissions to view.  

I hope this helps.

[Trudy Claspill]

@Fabian Lim 

Are you sure about this? Field Configuration don't affect the visibility of issues, to my knowledge. Field Configurations address, well, field configuration - whether the field is optional or required, visible or not, and custom descriptions that display with the fields.

How exactly would you use a field configuration to limit visibility of an issue?