Display issues from various jira projects without permissions restrictions

VINCENT DUPONT

Hello, 

I would like to let my project managers share some issues from their projects with the other project managers. For example all "put to production" events (with date). (cf release calendar)

This is easy to do for one project individually: create a filter on the projet (for example based on a Label or issuetype) and display the result of the filter in a Confluence Calendar.

But when having many projects with various users and permissions restricting access to the issues, how can I merge information from various projects in one result?

I've guessed these solutions but none seem perfect:

1. add all project managers into a group, add this group to all projects with a "Read only" permission. But then all projects are always visibles, anytime. This will show the Projects, issues, Labels, Versions, etc from all projects. that is annoying

2.create a dedicated project and ask project managers to create a specific issue in it describing each event. This is duplicate work (although this would be a better way of managing Production Requests, but anyway...)

3. use automation to duplicate all target issues from all projects into a new (unique) project where every project manager can read. Then we have to sync all changes, status update etc. It seems technically complex

what is your proposal/idea?

thank you very much
Vincent

 

unknown

Hello @VINCENT DUPONT ,

While it would be helpful to know the specifics of your Jira setup, here's a general approach you can take to solve this.

Underestanding the Situation

• You have two projects: "Developers" (DEV) and "Support" (SUP)
• You want tasks for "Managers > DEV" (Deployed status) to be visible to "Managers > SUP" (In production status)

Let's break down the necessary permissions, starting form the broadset to the most specific:

1. Global Permissions: Browse users and groups: Both sets of managers need this to see the select users/groups in Jira.
2. Project Permissions (Permissions Scheme): Browse Projects: Both sets of managers needs this to see the projects and thjeir issues.
   
   

Key Questions:

• Do both projects (DEV and SUP) share the same permissions scheme? This impacts how you'll adjust permissions.
• What level of access do you have in Jira? This determines which options are available to you (e.g., modify schemes, creating groups).

 

Assuming both projects share the same permission scheme, here are a few approaches:

• Groups: If this is a one-off situation, creating a new group and adding both sets of managers to it might be sufficient. This depends of your Jira permissions.
• Project Roles: If you have permissions, you can create a common project role for both sets of managers and grant it the "Browse Projects" permission in the scheme.

 

Now that both sets of managers can see the projects, let's filter which task they see, also taking into account the rest of the team, depending on the assignment of these managers, they may or may not share with the members of their respective teams.

• Filters and Boards: Create a filter that combines issues from both projects, filtering by issue type and status (Deployed and In Production). Then, create a board with this filter and share it only with the managers.
• Issue Security Scheme: If you need stricter control. Assign a security level (e.g., "department") to issues in each project. This way, managers from one department won't see the other department's issues unless the issue security level is adjusted accordingly.

 

Issue security schemes can help you fine-tune who sees what. It is good practice when granting cross-project access, be mindful of restricting visibility to sensitive information.

I hope this has been helpful and given you some ideas on how to approach this using the various tools available in Jira.

 

Feel free to ask whenever you need if you have any further questions or need more specific guidance tailored to your Jira setup!

We are here to help!

Regards,
Sergio G.