Getting Started with JIRA - Team-Managed Projects vs Company-Managed Projects

This video tutorial explains the differences between team managed and company managed projects in JIRA. Team managed projects, introduced in 2018, are easy to set up and do not require JIRA admin permissions, as all entities are contained within the project. In contrast, company managed projects require admin permissions because entities can be shared across projects. The video highlights the ease of use and setup of team managed projects, while company managed projects offer more complexity and shared resources. The tutorial concludes with a recap and a transition to the next video on creating a team managed project.

When were team managed projects first introduced in JIRA?

• 2002

• 2018

• 2021

• 2015

What is a key characteristic of team managed projects in JIRA?

• They require JIRA admin permissions to create.

• Entities can be shared across multiple projects.

• They do not require JIRA admin permissions to create.

• They were introduced in 2002.

Why do company managed projects require JIRA admin permissions?

• Because they are simpler to maintain.

• Because they are faster to set up.

• Because they were introduced in 2021.

• Because entities are shared across projects.

What happens if you create a custom issue type in a team managed project?

• It can be used in any other team managed project.

• It can be used in any company managed project.

• It only exists within that specific team managed project.

• It requires JIRA admin permissions to use.

What is a benefit of team managed projects?

• They are complex to set up.

• They share entities across all projects.

• They require global permissions.

• They are easy to set up and maintain.