How to Transition from Team Managed to Company Managed Projects in Jira

Introduction

Transitioning from a team managed to a company managed project in Jira can be crucial for overcoming limitations and maximizing project capabilities. This blog explores the process and key steps involved in making this transition.

Converting Team Managed Project to Company Managed

• The default setting in Jira for new teams is a team managed project, which works well for small teams and is easy to configure.

• However, team managed projects have limitations when it comes to working collaboratively with other teams and scaling agile.

• Issues in team managed projects are confined to that project and cannot be shared across different teams, which is a major drawback.

• Additionally, team managed projects are not visible in the advanced roadmap, limiting their potential for integration into a wider master plan.

• From an administrative perspective, making changes across multiple team managed projects can be laborious due to isolated configurations for each project.

Blog Segment: Transitioning from Team Managed to Company Managed Projects in Jira

• Transitioning from a team managed to a company managed project in Jira can be essential for overcoming certain limitations and maximizing project capabilities.

• One significant limitation faced by users of Jira’s team managed project is the lack of scalability and advanced functionalities, which often becomes apparent as the project progresses.

• Many YouTubers recommend team managed projects, however, transitioning to a company managed project can offer more flexibility and features that better suit the evolving needs of a project.

• To make the transition, users need to create a new company managed project in Jira, essentially creating two copies of the same project due to the unique name and key restrictions.

• The process involves adding a ‘c’ to the key and the word ‘company’ to the project name to differentiate it from the team managed project.

• After creating the company managed project, the next steps involve migration, deletion of the team managed project, and then making the necessary changes to the company managed project.

• It’s important to note that there is no direct button or simple process to convert a team managed project to a company managed project, requiring a series of specific steps to be followed for a successful transition.

Managing Company-Managed Projects in Jira

• To manage company-managed projects in Jira, the first step is to create a company-managed destination project with similar parameters to the team-managed project.

• When creating the company-managed project, it’s essential to ensure that you have the necessary administrative permissions in both the source and destination projects to enable issue migration.

• For issue migration, it’s important to note that the process only works for a maximum of 1000 issues at a time. If there are more than 1000 issues, they need to be migrated in batches.

• To preserve relationships such as epic story and subtask relationships during migration, clever filters and queries need to be developed to ensure that groupings maintain their connections.

• Administrative permissions are crucial for moving issues from the source to the destination project. It’s important to be a project administrator in both projects to successfully move the issues.

Moving Projects and Epics in Jira

• When moving projects and epics in Jira, there are some key steps to follow to ensure a smooth transition.

• First, when selecting the new destination project, be cautious about potential errors that can occur due to the manual movement of items.

• It’s important to double check and ensure that the epic-to-epic change doesn’t occur automatically, as this can lead to issues with the relationship between the epic and the story.

• When dealing with different workflows in the new project, it’s essential to map the existing statuses to the new project’s statuses, which may require some adjustments and careful consideration.

• For epics in a team managed project, it’s crucial to change the epic name to ‘change me’ to facilitate an easier transition and maintain the relationship with the stories.

• After completing these steps, confirming the changes and letting Jira perform the migration, it’s important to refresh the page to ensure that the migration was successful.

Migration Process for Project Management

• The process involves moving all the issues and sprint data from the old project to the company-managed project.

• The first step after the migration is to navigate to the company-managed project and organize the issues under epics and stories.

• Each epic needs to be manually updated by copying the title and changing the Epic name to match it, ensuring that all stories are nested underneath the correct epics.

• The migration process can be time-consuming, especially if there are a large number of epics to update, but it is crucial for maintaining the organization of the project.

• Efficiencies in the migration process are welcomed, and the author invites suggestions for alternative methods to streamline the process.

• Once the migration is complete, the next step is to manage access to the source project, either by shutting it down or deleting it for reuse of key or name.

Conclusion

Transitioning from a team managed to a company managed project in Jira offers the flexibility and advanced features needed for scaling agile and collaborative work. By following the outlined steps and best practices, users can successfully overcome limitations and optimize their project management capabilities.

undefined