Issue Summary

When a Jira Cloud site has only team-managed projects and no company-managed projects, users cannot add global custom fields to their team-managed projects. Instead, they see the following message:

"No more fields available — Project contains all the fields that have been created in your site."

This occurs even though the custom field's scope and context are set to global. 

Steps to Reproduce

1. Have a Jira cloud site with only team-managed projects (no company-managed projects).
2. Create a global custom field (e.g., single select).
3. Navigate to a team-managed project and attempt to add the field.
4. Observe the error: "No more fields available."

Expected Results

• Any custom field with global context should appear in the “Add field” dialogue for team-managed projects.
• Customers who exclusively use team-managed projects should still be able to:

               Create global custom fields.
                Reuse those global fields across their team-managed projects without needing a company-managed project as a prerequisite.

Actual Results

• On sites that have no company-managed projects, when users attempt to add a global custom field to a team-managed project, they see:

“No more fields available – Project contains all the fields that have been created in your site.”

• The global custom field:

                > Does not appear in the list of available fields to add.

                > Can't be associated with the team-managed project, even though the field context is set to Global.                           

• In another instance (with company-managed projects), the same field type can be added successfully to a team-managed project, indicating the behaviour is inconsistent and likely dependent on site/project setup rather than field configuration.

Workaround

Create a test or placeholder company-managed project on the site. Once a CMP project exists, the global custom fields become accessible and can be added to team-managed projects.

⚠️ This is not an ideal long-term solution and should not be required for customers who exclusively use team-managed projects.