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!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Are project/client based issue templates a thing?

I'd like a way to create, manage, and enforce custom pre-population of issue fields to achieve 3 particular goals.

1.) Increase the speed at which backlogs can be backfilled for specific projects. (no need to manually set fields for each field in a ticket.)

2.) Decrease the occurrence of missing information, or incomplete ticket information.

3.) Have granular control over distinct "sets" (or types) of tickets to be entered. To clarify, I'd like to be able to have my product designer have access to one "type" of feature ticket that is filled out according to a template specific to their needs/function, and another "type" of feature ticket that is filled according to another template specific to the needs of a developer, or a QA, or a stakeholder, etc.

I'm not sure what would provide this functionality specifically, or if there's a workaround to implement it, but any insights, suggestions, or use-cases would be greatly appreciated.

1 answer

0 votes

Hello Ben,

Welcome to Atlassian Community!

When creating a ticket, currently the only way to let fields filled is by adding default values. Templates were never an option natively in Jira, so there is a feature request opened since 2005 suggesting the implementation of this ability:

For now, the workaround would be using an add-on. I found two that may help you:

Hope this helps!


Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events