I would like to streamline the information entered in Jira when the users create issue/task/goals.
How do I make sure they get to enter the description field based on pre populated text?
Hi everyone,
This feels like a fairly common ask for Jira. I understand that some users would like to create new issues within Jira that follow some kind of pre-populated data in order to streamline the ticket creation process.
Some users are seeking to be able to set a default value for system fields like Description, but on a per project basis. This alone might meet the ask of issue templates for some users but not others. If you’re using Jira Cloud next-gen projects, this feature exists already within next-gen projects. Customize an issue's fields in next-gen projects has more details on exactly how you can do this today.
As for non-next-gen projects, setting default values to system fields is still something we are tracking feature requests for in JRASERVER-4812 for Jira Server and JRACLOUD-4812 for Jira Cloud. I recommend that if this is a feature you want to see in Jira natively, please vote on the respective issue here to help our development team prioritize new features. You can also watch those issues to get updates to them. At the time of writing this update, the Server team has moved this issue to in progress as it appears this is actively being worked on.
In the meantime, there are a number of third party solutions that already exist for this that can be found in our Marketplace.
Andy
Usually, a desire for "templates" in Jira means you've got a set of fields you don't actually need.
Which is why there's no templating system built in.
And you absolutely do not want "pre populated text" in text fields - you can guarantee you will end up with piles of issues with just that text in there and nothing of any use.
But, if you insist, then have a look in the marketplace - there are Apps to do Jira templates.
Thank you Nic for the details.
I agree to your point that if I pre populate text/label people may not fill up the details while creating the ticket.
However the problem I am facing is, even without that I have n number of tickets created by team without any useful information in it. This is something I would like to avoid.
Ex: If I need everyone to log a ticket for vacations they are taking, I would like it in a predefined format. Similarly the use stories or bugs could be logged in a specific format, like steps to reproduce, link where the feature is broken etc
How do you suggest I tackle these?
Set up different issue types with the fields you need to capture, and leave off fields you don't need for each type. That obviates the need for templates, as you're only asking for stuff you need.
Hi @Smita
You may benefit from Easy Templates for Jira add-on. It allows you to create a Template per issue type like Story, Task, Bug containing subtasks.
Once you create an issue from the Template - subtasks will be automatically populated.
Cheers,
Pavel
What about a repeatable task that contains a checklist of steps required to complete the task? The template would have the checklist already created...?
Thanks!
The ticket covering this probably has it's driver's license (depending on the state): https://jira.atlassian.com/browse/JRASERVER-4812
Having the ability to save and reuse issue templates would be a wonderful and simple addition to JIRA, so that issue-reporters would not have to waste time and brainpower on extraneous questions every time they write a ticket: e.g., what H-level should headings that appear in every ticket be formatted with, and what sort of bullet styling should be used for conditions of satisfaction. This would also be helpful for onboarding, in teams with lots of turnover.
These are all actual decisions that humans need to make. Making them at all is a distraction and waste of time. Making them the wrong way can result in both technical and social inefficiencies. Templates would eliminate these inefficiencies.
I use Automation, and create a rule for pre-populating for certain issues
Is Automation available for next gen projects? if yes how do i enable it? thanks
Project settings -> Apps -> Project Automation
Having to rely on automation to have templates feels broken to me.
I find that many here talk about issues, and I would agree that having templates for issues to prepopulate information such as what you expect to see in the description is a good thing.
But, there are also other categories of requests users can make of a service desk. ITIL calls them Standard Requests. For instance you are onboarding an employee. You need HR to create accounts, IT to create accounts, Provision a computer, etc... All these tasks and steps are required for each onboarding. Same for offboarding. Not having templates means people have to remember what tasks they have to do... or refer to a job aid or other documentation...
With templates not being available, I will be looking at another tool to handle our service desk.
This is perfect! Automation can create subtasks in a templated fashion -- exactly what I needed.
Hi @Paul Pavlovsky_AppLiger_ , with this add-on, is the template available for all users ? Is it possible to configure some template for some users roles ?Best regards
Hi,
Saved templates are available for all users who have an access to projects where the templates might be used. At this moment, there's no possibility to define access per user role.
I've added this as feature request and started gathering users votes/opinions.
Thanks,
Any updates on the JIra Template for JIRA Cloud?
one year later and you still have not implemented it? Can you please tell me why somebody needs to pay extra for plugins to do something possible in the JIRA server and is it possible on team-managed projects but not company ones?Unbelievable
I think we're missing part of the point.
Bad templates create junk, and inefficiencies. It's easy to use them and other functionality to automate our own stupidity.
It's also true that good templates allow for efficient mass customization, and introduce quality control, the latter vis-à-vis checklists. I want to make sure that I check all 9 things every time I get a bug, but I also want to make sure that everyone else that receives bugs checks those 9 things. Process improvement is more about how you use your tools and less about which tools you use.
If Atlassian chose not to introduce native template functionality, ok, but if they chose not to do it because it only introduces junk, then they're avoiding it for the wrong reason.
And buying even a simple an add-on as a stopgap is a long process in medium- to large-sized companies. I'd like to have this as part of Jira's OOTB functionality.
I am also missing issue templates. It's something I have previously been using when working with Azure DevOps, and in most cases it actually worked really fine and did not lead to problems.
One use case was that of bug templates. So based on the universal bug type, we were creating e.g. a security bug template which was pre-populating a few fields that were properly identifying the issue as a security bug. Or when running a larger bug bash, we created a bug template that would always add a certain label to the item, that way we were able to see which bugs had been created during the bug bash.
Currently, my need is to structure the creating of stories/epics/initiatives more and having a templating mechanism would be really helpful.
Hello @Ralf Gautschi
It's Aleksandra from Deviniti, the vendor of the Issue Templates for Jira app.
If you're looking for templates functionality that would allow you to populate fields values automatically from template, I encourage you to give our app a try. In short, the app not only allows to copy over various fields' values from template, but also create more complex structures with just few clicks that may include Epics, Stories, Tasks with Sub-tasks, and any additional issue links.
The app is currently available for all hosting options including Jira Server/DC and Cloud. Hopefully, you will find it useful!
Cheers,Aleksandra
More like… 20 years.
Still a very much needed feature for company-managed projects!
If anyone is still interested in an app for issue templates, we have a paid plugin on the marketplace called STM. This powerful tool allows you to create and update issues using templates. You can apply these templates manually or automatically during issue creation, status transitions, or field value changes.
Key Features of STM:
Check out our marketplace listing and detailed documentation for more information.
Feel free to ask any questions to support@redmoonsoftware.com
Thanks
Paul
There is a free app - Issue Templates Picker - Summary, Description and more which allows to create issue templates in a project.
Cheers,Mario
It looks like you're new here. Sign in or register to get started.
