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!
Hi! My name is Eoin and I'm a product manager working on Team-managed projects in Jira Software Cloud. We're continuously improving and updating Jira Software and feedback from our customers is ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events