Need to restrict shared teams to only one project

[Jeff Davis]

I am working on Jira Server 8.20.10 in an environment with multiple Jira projects. In standing up a new project, Project A, I have created shared teams so that people in that project can select the correct team assigned to an issue.

In an entirely different Jira project, Project B, users are able to select the teams I created for the new Jira project.

I don't want Project B users or any other users not involved in Project A to be able to select Project A teams (or see anything Project A-related). I am the project lead for Project A so I should not be very limited in what I can do, but I can't determine how to modify permissions properly. Restricting the teams within the plan even to just me wasn't effective.

I would appreciate some step-by-step instructions on how I can keep Project A stuff visible only to people granted access to that project.

[Oday Rafeh]

Hi @Jeff Davis , 

To restrict the visibility of shared teams to only one project in Jira Server, you can't do it directly, as shared teams are designed to be accessible across multiple projects.

However, you can use a workaround by creating custom fields to store team information and setting the appropriate field configuration schemes for each project.

Here's how to achieve this:

1. Create a custom field for team information:
   a. Go to Jira Administration (the gear icon) > Issues > Custom fields.
   b. Click "Add custom field" and choose a field type ("Select List (single choice)") to store team information.
   c. Name the custom field ("Project A Team") and add the teams as options.
2. Create a field configuration scheme for Project A:
   a. Go to Jira Administration > Issues > Field configurations.
   b. Click "Add field configuration scheme, " name it ("Project A Field Configuration Scheme"), and click "Add. "
   c. Associate the "Project A Team" custom field with the new field configuration scheme by clicking "Configure" next to the scheme and then "Edit Default Field Configuration. "
   d. Find the "Project A Team" custom field and set it as "Required" or "Optional, " depending on your preference.
3. Apply the field configuration scheme to Project A:
   a. Go to Jira Administration > Projects, and locate Project A.
   b. Click on "Project settings" (the gear icon) in the bottom-left corner.
   c. Click on "Fields" in the left sidebar.
   d. Click "Actions" > "Use a different scheme, " and select the "Project A Field Configuration Scheme" created in step 2.
4. Remove the shared team field from Project B:
   a. Follow the same process as in step 3, but for Project B.
   b. Make sure not to associate the "Project A Team" custom field with Project B's field configuration scheme.

Then you will have a separate custom field for team information in Project A, which will not be visible to users in Project B or any other project. Please note that this workaround might require extra effort to manage, as you'll need to create and maintain separate custom fields for each project where you want to restrict team visibility.

Hope this will help, 

Best Regards

[Jeff Davis]

@Oday Rafeh it seems I don't have permissions to do this, even though I'm listed as the project lead. The team that owns this development environment still keeps some things to themselves. I'm going to engage with them and report back (and hopefully click Accept answer, too). Thank you!

[Oday Rafeh]

Thanks for the feedback @Jeff Davis, I hope my answer helps you and if you have any questions related let me know and I will happy to help.

Regards 

Oday 

[Kristján Geir Mathiesen]

Hi @Jeff Davis 

Good question and I am commenting to follow the discussion.

I am not aware that this can be done, at least not with OOTB Jira.

Best, KGM