- Get started
- About
- First steps
- Glossary
- Migration to Cloud
- Configuration
- Global configuration
- Repository
- Template configuration
- Template scope
- Manage templates
- Supported fields
- Permissions
- Using templates
- Create issue from template
- Create issue structures
- Apply template to existing issue
- Recreate issue
- Use template custom field on issue create screen
- Default templates
- Direct link
- JQL searchers
- Variables
- Static variables
- Dynamic variables
- Smart defaults
- Basics
- Smart issues
- Smart users
- Smart dates
- Smart project
- How to use smart defaults
- App Integrations
- Team-managed projects
- Jira Software
- Jira Service Management
- Advanced Roadmaps
- Issue Checklist for Jira
- Advanced
- Automation
- Legacy automation action
- REST API
- Create issue and apply template with Jira REST API
- Security
- Security statement
- App permissions
Team-managed projects
This chapter provides information on how to use templates in team-managed projects.
Team-managed projects differ much from company-managed projects. The main difference is that most entities, like issue types or fields, are local to a team-managed project.
Entities form different projects may have the same name, but from the technical view, they are not the same. This complicates matching entities between different projects and makes copying fields problematic.
The Issue Templates for Jira app matches issue types by name, which works well for team-managed projects. However, at the moment there is no solution for matching custom fields by name. This functionality is on top of our backlog.
Differences between company and team-managed projects that affects ITC:
- Company-managed projects can share the same custom fields and issue types, team-managed entities are local and are not shared
- Subtasks can’t be created directly under Epic in team-managed projects. Other issues (like Story or Task) still can have subtasks as in classic projects
