- Get started
- About
- Glossary
- First steps
- Migration to Cloud
- Integrations points
- Create issue from template
- Recreate issue
- Apply template
- Apply template post function
- Legacy automation action
- Template custom field on issue create screen
- Apply template via issue property
- Configuration
- Repository
- Template's configuration
- Using templates
- Copy Epic
- Copy links and linked issues
- Copy Subtasks
- Copy Initiatives
- Default templates
- Using Variables
- Static variables
- Dynamic variables
- Smart defaults
- Basics
- Smart issues
- Smart users
- Smart dates
- Smart project
- How to use smart defaults
- 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
