It’s important to bring efficiency to your Jira admin team. While there are a few things that seem obvious, it’s not something that every team does. Today, I’ll talk about creating default templates for your instance.
Jira’s base templates are fine for building, but the slight problem is that Jira creates individual schemes for every project. While there are benefits to this, it also creates a very messy experience for admins. This is when creating a default template for certain project types will benefit your process.
Here are the examples of when shared default templates are a benefit:
- Projects with shared templates are easier to update
- For some teams, it’s important to have the same project template
- For teams or companies that need to maintain certain standards or compliance, shared templates will provide that baseline
- Schemes are easier to maintain
To make shared default configurations work for your instance, you’ll need to define what the baseline is for certain project types.
For example, an engineering team might have the following process: Open ticket -> In progress -> In QA -> In Stage -> Released -> Closed. This shared workflow can be created and associated to all engineering projects.
They might also require that only team leads are able to manage sprints. Now you have two shared items between engineering teams - workflows and permissions. In this case it is much easier to create a shared default template than it is to remember to associate these schemes to each engineering project.
Let’s say that the engineering teams also need to have shared issue types. The teams trade issues back and forth between each team. Adding a default issue type scheme to the default template will make it so that every time an engineering project is created, it already meets the standard requirements.
Now, if at any point in the future there needs to be a change across all engineering projects, it’s an easy fix. The admin won’t have to update multiple project schemes, they’ll just need to update the default template.
For admins, looking at project configurations often leads to pages of scrolling to find the right scheme, workflow, or screen. By consolidating projects that share the same team or process, it cleans up duplicate schemes, makes it easier to maintain projects, and ensures that admins aren’t spending unnecessary time on overhead.