Time Managed Software vs Company Managed Project differences?

Monalisa_Azzopardi_chartwell_com
Contributor
November 27, 2024

Hello,

I have seen some projects within my organization using Time Managed Software vs Company Managed Project using SCRUM 

Can you please tell me the following:

  1. What is the difference between the two?
  2. When should each of the different projects be used?
  3. I like Time Managed Software but I found two issues versus when using Company managed software - A.  Backlog:  Company managed does not show me the due dates in my field vs Time Managed.  B.  Time managed does not allow me to use the time tracking report.  Why would these features not be available in both types of projects?
  4. What needs to be done to have the features available in both types?

Please note, I am not looking for responses for add-ons or additional purchases as of now we are being asked to use what is being offered so I do hope I can get responses based on this requirement

Thank you

 

3 answers

1 vote
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
November 27, 2024

Hello @Monalisa_Azzopardi_chartwell_com 

I believe you mean "Team" Managed rather than "Time" Managed.

Here is one reference on the differences.

https://support.atlassian.com/jira-software-cloud/docs/what-are-team-managed-and-company-managed-projects/

There are additional links on that page to more information.

As mentioned on those pages one consideration for which project should be used is how you want to manage customizations in the project. For Company Managed projects the customizations are managed by Jira Admins. For Team Managed projects the customizations are managed by the Project Administrators.

Company Managed is the original project architecture. Team Managed was developed later.

I can't speak to why Atlassian chose to incorporate some functionality and not others into Team Managed projects. In some cases it may be that certain functionality was prioritized for inclusion at a later date.

It is not possible for you to make the unsupported features available in the other project type. There may or may not  be workarounds available using native Jira features.

For 3a you can add the Due date field to the card layout in the Board configuration.

For 3b I'm not aware of a workaround. There is a change request for the report to be added, to which you can add your vote.

https://Jira atlassian.com/browse/JSWCLOUD-18009

0 votes
Prachi Bolar
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
November 27, 2024

Hi @Monalisa_Azzopardi_chartwell_com 

Welcome to community :) 

Please find the details here : https://support.atlassian.com/jira-software-cloud/docs/what-are-team-managed-and-company-managed-projects/

Key difference 

- Team managed has 1-1 mapping, 1 board 1 project and doesn't have board filter to share the board with other company managed or have multiple boards, where as company managed can do this

- also team managed is more for smaller projects. Its permission scheme, workflows cannot be share with other projects while company managed we can

- please refer to issue limits in tmp and cmp https://support.atlassian.com/jira-software-cloud/docs/issue-limits-in-team-managed-projects/ and https://support.atlassian.com/jira-software-cloud/docs/issue-limits-in-company-managed-projects/

- Team managed can have only subtask while company managed can have multiple subtask created 

 

Thank you,

Prachi

 

0 votes
John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
November 27, 2024

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events