• Products
  • Documentation
  • Resources

Limitations of team-managed projects in your plan

This page refers to the advanced planning features that are only available as part of Jira Cloud Premium and Enterprise.


As of July 2023, your plan now supports team-managed projects. You can add them to your plan like you would any other issue source. Learn how to add a project, board, or filter to your plan.

That said, there are a few things that team-managed projects can’t yet do in your plan.

Team-managed custom fields can only be applied to issues from the project in which they were created

While globally-scoped custom fields can be used across all issues in your plan, custom fields from team-managed projects can only be applied to issues from the same project in which the field was configured.

If you want to use a team-managed custom field across multiple projects, we recommend converting it to a globally-scoped custom field. Learn more about custom fields.

Level 0 (story level) issues from team-managed projects need to stay in the project in which they were created

Your plan doesn’t allow you to reparent a task or story from a team-managed project to an issue from a company-managed project.

Exclusion rules only apply to issues from company-managed projects

Exclusion rules use globally-defined issue types and statuses, which are used in company-managed projects. Statuses and issue types from team-managed projects, even if they’re the same as their company-managed counterparts, won’t appear in the search box.

Existing exclusion rules in your plan won’t be applied to any team-managed projects you add. Read more about exclusion rules.

Still need help?

The Atlassian Community is here for you.