Limitations to linking Jira Teams to Projects "One project or space can have up to 15 linked teams"

[Hunter Lardy]

We are starting a new project and wanted to try using Jira Teams as an additional way to organize work. 

When we open the Jira Team Number 16 page and attempt to add a project link, we get an error message: 

"One project or space can have up to 15 linked teams. Unlink an existing team first, then link the new team to the project or space"

I tried looking through Jira support articles related to teams and couldn't find this limitation listed anywhere. Teams in Jira projects | Platform experiences | Atlassian Support

If we already have the project loaded with 15 Jira teams and attempt to add Team Number 16 to the Team field in a work item, it will not allow us. 

• Does anyone else experience this limitation? 

• Is there documentation related to Jira Teams I'm missing? 

[Hari Krishna · Accepted solution]

Hi @Hunter Lardy

Yes, this is a known limitation in Jira — even though it’s not clearly mentioned in the documentation.

A single project or space can be linked to **maximum 15 Jira Teams**. That’s why you’re getting the error when trying to add Team #16.

To fix this:
1. Go to https://teams.atlassian.com
2. Unlink the project from one of the existing 15 teams
3. Now you’ll be able to link Team #16

There’s no way to increase the limit as of now. You’re not missing any doc — it’s just an undocumented platform restriction.

[April Chi]

Hey @Hunter Lardy ,

Hope you're well and thanks for sharing. I'm the product manager in Teams App working on this feature. 

Apologies if it was unclear - we'll work on adding this to the documentation itself. 

May I ask how your teams work in your organization? For example:

- Do multiple teams work in a single Jira project? How many teams usually and how significant is the contribution of each team?

- Is there an 'owning' team? i.e. a single team technically 'owns' this Jira project? 

- Would also be great to understand the types of Jira projects i.e. are they long-term projects or shorter-term projects.

All this would help us understand whether we should address this limitation. Let me know if you have any feedback!

[Hunter Lardy]

Good morning April, thanks for chiming in. 

1. Most of our projects in Jira currently are not utilizing the Team field. If they are, the individual project leads / managers are organizing their projects with Teams themselves. I as the admin don't put any limitations or guidelines on PMs doing this. 

2. No. Several project managers will be responsible for organizing and owning their projects. I'll help with workflows, issue fields, etc.. as they get acquainted with Jira (our organization is relatively new to Jira, < 1 year). 

3. This specific project is a multi-year program that will have stakeholders from multiple departments. We hoped to use the Teams field to organize backlogs for a couple of different boards, then create swim lanes in those boards for each Team involved. 

We are planning to continue using Teams as described in point 3. I believe we can consolidate some teams to get around the limitation. 

Appreciate you offering to add it to the documentation. It's nice to know these things before we start implementing our design in the site. 

Have a good day!