Getting Started with JIRA - Creating a Company-Managed Project

The video tutorial explains how to create company managed projects in JIRA, highlighting the need for administrative permissions. It covers selecting project templates, understanding template access restrictions, and the benefits of using company managed projects for teams. The tutorial also emphasizes the importance of choosing the right template based on team goals and workflows, and discusses the licensing requirements for certain templates.

What is a key requirement for creating a company-managed project in JIRA?

• Having JIRA administrative permissions

• Using a Kanban workflow

• Being part of the marketing team

• Having a JIRA service management license

Why is it important to understand team goals when selecting a project template?

• To avoid using locked templates

• To reduce the cost of the JIRA license

• To switch between project types easily

• To ensure the template aligns with the team's objectives

What does a locked template in JIRA indicate?

• The template is outdated

• The template requires features not included in your current license

• The template is only for team-managed projects

• The template is for administrative use only

Can you switch a company-managed project to a team-managed project in JIRA?

• No, unless you have a special license

• Yes, but only with administrative permissions

• Yes, at any time

• No, you must create a new project

What is a benefit of using company-managed projects for teams?

• They are cheaper than team-managed projects

• They allow sharing of issue types and workflows across multiple projects

• They do not require administrative permissions

• They automatically update with new JIRA features