Global repository
Define a Jira project as a global repository to store and manage reusable issue templates across multiple teams.
📦 What Is the Global Repository?
The Global Repository is a designated Jira project used to store issue templates that can be applied across your entire Jira instance. It acts as a shared source of truth for reusable templates, enabling standardization without duplication.
Rather than maintaining separate templates per project, you can define global templates once and make them available wherever needed.
🌍 Why Use a Global Repository?
In many organizations, the structure of issues — especially onboarding tasks, bug reports, or epics — is similar across projects. By storing templates in a single, centralized location, you gain:
✅ Consistency – use the same templates across teams and departments
✅ Maintainability – update a template once and apply improvements everywhere
✅ Scalability – reduce clutter by avoiding duplicate templates per project
✅ Simplicity – manage templates in one place without switching contexts
The Global Repository ensures you’re not reinventing the wheel every time a new project needs structured issue creation.
⚙️ How It Works
You can select any existing Jira project to serve as the global repository
This project will be treated as the template space, and any issues marked as templates within it will be available globally
By default, every issue created in the Global Repository project is treated as an active issue template. If needed, you can still disable individual templates using the visibility setting in the Issue Template panel on the issue view.
Templates stored in the global repository behave exactly like any other issue templates. They can be:
Applied manually (via the template picker or issue panel)
Used as default templates for specific projects and issue types
🧪 Interactive Demo
The interactive demo below shows you:
How to create or select a Jira project
How to mark it as the Global Template Repository in the Templify configuration
How templates stored there become instantly available across your instance
Tip: You can change or remove the global repository at any time in the configuration settings.
✅ Best Practices
Use a neutral name like
Template RepositoryorTemplate Libraryfor your repository projectRestrict who can create or edit templates in that project (e.g., only team leads or admins)
Keep actual issues in this project marked as templates only — don’t mix them with real project work
Last updated