Atlassian Jira

Best Practices for Creating a Jira Issue With Templates

This is a guest blog post written by the Globo Solutions team. In this blog post, they highlighted the best practices you can use to create Jira issues with templates.

 

Jira indeed is a global solution. Thousands of people around the globe not only use it at work but also cannot imagine their lives without Jira. Users create so many tasks on a daily basis!

Have you ever wondered how much time we spend on creating issues or collecting missing information in issues? While it is minutes on a scale of one issue, but hours within a project, and even days for the whole Jira instance.

Various respected companies tend to find solutions that would help them optimize the issue creation process and minimize time costs. In this blog post, we will describe three ways to get this done:

  1. Out-of-the-box Jira capabilities
  2. Apps from the Marketplace that allow you to create issues with templates
  3. The Field Templates for Jira app

1. Tune-up your project in Jira

Buying an app is easy, but not all companies can afford it. So, the first option is exactly for them.

Jira allows setting descriptions for each of its fields individually out of the box. By adding field description or just inserting a link to documentation, you help users understand the rules and specifics of this particular field, saving your team’s time.

You can also use direct links to create issues. For example, if you click the link on a Confluence page, it will open the issue create screen. Some of these links may have prepopulated fields. It works the same as if you clicked on the Create button in Jira, but its fields already have all the information right where it belongs. You can read more details about this feature here.

2. Сreate issues with templates

The out-of-the-box Jira capabilities can be handy, but not for every case. Here comes the Atlassian Marketplace. Lots of vendors offer their apps for almost every possible challenge. Just type the word “Templates” in the search field on the Atlassian Marketplace, and you instantly get a variety of add-ons for creating issue templates. That would be the second option to pay attention to.

These apps have similar features as they let users save time on populating issue fields with the help of issue templates. You just need to pick the right template from the list. It is quite handy when you create lots of similar tasks.

In addition to that, other apps can create templates based on other tasks. These issues will have the same content as the original one. Similar to the native Jira Copy action but in a smoother way. It helps users optimize processes and save time, but it has its drawbacks. Setting up such templates is not a trivial operation. At first sight, it is not clear how to use it and how it all works. Note that you cannot combine the values of different fields. You have to create a separate template, thus multiplying them endlessly. Each time you need to combine field values from different templates. Any plugin will make you create a new template. This particular method gives you no other option.

3. Сustomize your templates for different needs

Yet the third option every user has at their disposal is the Field Templates for Jira app. This add-on is an alternative solution for issue templates. With its help, you can create templates for both system and custom text fields. Splitting templates visibility by project roles, issue screens, and types makes it more adaptive to every process and team.

You no longer need to reinvent issue summary or spend time on how to create issue description. All you need to do is to select the template for the current situation and fill in the rest if necessary. Combining templates is not only possible but welcomed.

As a result, it greatly speeds up the issue creation process for reporters. The ability to create comment templates not only on the project level but for each user individually is a nice bonus of this solution.

Resume

These are just three solutions out of many that we decided to describe for you. Still and always you are to choose what’s best for your business as every method has its advantages and disadvantages.

Here is a brief summary of all the above-mentioned solutions:

Solution Intuitive UI Flexibility Rich functionality Easy to set up Easy to use Personal templates Field types support Free
Native Jira tools

(minus)

(minus) (minus) (minus) (plus) (minus) (plus) (plus)
Issue Templates apps (plus) (plus) (plus) (minus) (plus) (minus) (plus) (minus)
Field Templates for Jira (plus) (plus) (plus) (plus) (plus) (plus) (minus) (minus)