Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Issue Templates - our team's favourite App for templating and creating structured issues

Daniel Ebers
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Jul 26, 2021

Today we want to share our favourite App with you.
It is called "Issue Templates for Jira" from Deviniti.

Why did we look for a templating App and how did we find the app?

Many years back when we setup our first-ever instance of Jira teams did not consider the backgrounds behind custom fields. Nearly everbody could create a custom field. The instance became not manageable - we had to create a new one, from ground up.

There were several meetings to consider how it could be done 'better' - same time information the requirement was that information still should be possible to enter into an issue in a structured manner!

Our teams back then took a closer look into templating solutions and found Issue Templates from Deviniti by comparing several solutions from Marketplace.

What do we use it for and who are the key users?

Meanwhile many teams use the advantages of templating - we rarely need to create new custom fields.
In case no reporting will be needed for data then we always recommend to use a template and to put information into a multi-line text field named like 'More information'.
The advantage is: during issue creation an user can fill in fields - just like they are familiar with but after the issue is created and stored in database those data are filled into one single custom field.

For a few weeks now we extensively use a further feature of Issue Templates - creating a structure during issue creation.
Given an example it works like this: teams create a template for a repeating task and define that every time this template is used also a Sub-Task should be created.
This makes it easier for teams not having to remember which structure they need to create exactly and how. Especially for task which requires nearly a dozen ob Sub-Tasks to be created this is a huge relief.

What would happen if we didn’t have it?

Likely the new Jira instance would also have hundreds of custom fields meanwhile. We believe that the manual creation of structures is prone to errors, having potential to decrease productivity and user satisfaction.

Therefore we really appreciate Issue Templates can help us powering even complex processes and find the support from Deviniti always helpful, professional.
Issue Templates is a very stable App, cases where we needed customer support are rare. We are still happy that in those cases a reaction comes fast and a solution could be found every single time in the past.




Log in or Sign up to comment
AUG Leaders

Atlassian Community Events