You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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.
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!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.