Why did your team disable team-managed projects?

[Christel Gray]

If your Atlassian support team disabled team-managed projects, I'm interested in learning your use case for doing so.

I've disabled their creation - for now at least - on our site. The major reason is when we have boards who's filters involve all projects across our instance, team-managed projects don't get returned in the results. Mainly because team-managed projects can't be returned on a company-managed board.

But tell me why your group has disabled them.

TIA!

[Samuel Gatica _ServiceRocket_]

Hi @Christel Gray 

As a Jira administrator, I have concerns regarding them, as they may compromise governance, consistency, and scalability across the Jira environment.

My reasons for disabling team-managed projects:

• Lack of Standardized Configuration
• Inconsistent Reporting and Dashboards
• Limited Access Control
• Limited Functionality and Integration
• Scalability and Maintenance Problems
• Potential for Conflicting Configurations

Best regards

Sam

[Christel Gray]

Thank you, Samuel. All valid reasons in my book!

[Trudy Claspill]

Hello @Christel Gray 

Actually, Team Managed project work items can be displayed in a board that is associated with a Company Managed project, if the filter is constructed correctly.

I have recommended to most of my clients that they disable the ability to create Team Managed projects because it can result in uncontrolled proliferation of custom fields and status that use the same names, and that can make filtering difficult and confusing to the uninitiated. Additionally, if there is a need to do cross project reporting it can cause problems because the TM project configurations can not be automatically forced to match CM project configurations.