Feature #643

Issue description templates

Added by Yonni Mendes almost 11 years ago. Updated over 1 year ago.

Status:NewStart date:2008-02-12
Priority:NormalDue date:
Assignee:-% Done:


Target version:Candidate for next major release


When opening new issues it would help guiding the user to be as detailed as possible if an administrator could create a predefined template per tracker (per project?). Such a template need only be displayed as stand in text in the description field so that the user can then replace template parts with the actual input.

Related issues

Related to Redmine - Patch #2931: Templating for description of new tickets by Tracker New
Related to Redmine - Feature #6715: Issue templates New 2010-10-20
Duplicated by Redmine - Feature #12807: Add template per project for new issue Closed
Duplicated by Redmine - Feature #3153: Default description text Closed 2009-04-10
Duplicated by Redmine - Feature #3594: Custom default value of the description field Closed 2009-07-07


#1 Updated by Thomas Lecavelier almost 11 years ago

I don't think it's a "want-have" feature:

Even if it should be a good idea to teach BTS usage to new users, they soon will be proficient in using it, so entering an issue using n pages will become time-consuming. Organizing a small meeting presenting the tool with some real-usage of the tool for each attendee should be more valuable.

(or maybe I haven't understand your idea :) )

#2 Updated by Ale Muñoz almost 11 years ago

+1 for this.

What he is suggesting is this:

- When the user clicks on "New Issue", the description field is pre-filled with a text like this:

What you did
Please describe what you were doing when you found the issue

Expected result
What were you expecting to happen?

Obtained result
What happened instead

Please tell us what is your operating system, version, browser, etc...

(or words to that effect)

Check http://twitter.com/help and you will understand. That form is a masterpiece of design, and is used a lot like a good example of how things should be done : )

#3 Updated by Jean-Philippe Lang almost 11 years ago

Check http://twitter.com/help and you will understand

You can have a pretty close result using custom fields.

#4 Updated by Adam Bates over 10 years ago

I was wondering if this suggestion would be revisited, as for a consistency reason it would a great feature. We have three very different trackers which have three different purposes. It would be good to provide a template for the user to provide verbose responses within a structure.

#5 Updated by Light Kong over 8 years ago

Similar request to #2931.

#6 Updated by Mischa The Evil over 8 years ago

  • Subject changed from Description templates to Issue description templates
  • Category changed from UI to Issues

This is indeed related to patch #2931, which is related also to issue #1138 which itself seemed to be a duplicate of this issue. I've closed #1138 in favor of this older issue.
I've also modified this issues properties subject and category to make it easier to find.

#7 Updated by Erwin Mueller about 8 years ago


It would be great if you can specify a template per project and one to each issue category (bug/feature/support).
For example, what I like to have for issue type feature:




You can't have this with custom fields, because if you add custom fields, they will be under the description text field, below the standard fields, above the files upload field.

#8 Updated by Damien Couderc about 8 years ago

Hi all,
It would also be even more useful if it was possible to have multiple templates for multiple kind of issue of the same tracker.

#9 Updated by Antoine Roux almost 8 years ago

Yes, I would love to have that as well. One template per tracker would be perfect in my case.

#10 Updated by Sylvain Guimond over 7 years ago

+1 It would be useful!

#11 Updated by Sunil Babu over 7 years ago


#12 Updated by Josh Davidson over 7 years ago


#13 Updated by Terence Mill over 7 years ago

Templates shall support wiki marcos also

#14 Updated by tim lin over 7 years ago

+1, it would be very useful.

#15 Updated by Mike Rötgers over 7 years ago

+1, indeed very useful

#16 Updated by Andrey Zubkov about 7 years ago

+1 vote

#17 Updated by Slan Buas almost 7 years ago


#19 Updated by Anonymous over 6 years ago

+1 vote

#20 Updated by Jonas J over 6 years ago

+1 needs to be on trunk

#21 Updated by Etienne Massip almost 6 years ago

  • Target version set to Candidate for next major release

#22 Updated by Rodrigo Ramalho almost 6 years ago

+1 vote

#23 Updated by Olivier Houdas over 5 years ago

+1 vote
We had it in our previous BTS (home-made), and now that we are shifting to Redmine, this would be greatly appreciated.
Note that we allow everybody in the company to enter bugs, hence the need to be a bit directive on the description.

#24 Updated by Matthew Houston over 5 years ago

Not sure if the template ticket should have been closed as duplicated. http://www.redmine.org/issues/12807

I think this particular ticket is already addressed by the custom fields. If that info is required then a custom field can be created and set as required?

Templates on the other hand are a different matter. For instance we are managing store installations with Redmine and to be able to have a template with pre-filled relationships and sub-tasks based on different criteria that the user could select would be great.

At the moment we just have an existing issue with all sub-issues created and linked, but it doesn't cover nearly enough, having the user select from a list would be awesome! While it is handled currently by a plugin, the rapid rate of releases is seeing a lot of these plugins just fall by the wayside unfortunately...

#25 Updated by Anonymous over 5 years ago

+1 for a template per tracker and per project

#26 Updated by Gurvan Le Dromaguet about 5 years ago

+1. Have been using it for a long time the patch at http://www.redmine.org/issues/2931, simple and working !
UPDATE: I am wrong sorry, there is a bug: when changing the Tracker of the new issue, template is not updated.

#27 Updated by Ilya Demenkov about 5 years ago

+1 vote.

We are currently using http://www.r-labs.org/projects/issue-template plugin as advised by John McBade at #11210 for this, but its features are limited, not not mention it's better to have such feature built-in.

As I've described in #11210, such feature should allow to set default values for most fields of an issues, not just for its description.

#28 Updated by Alessio Pollero about 5 years ago

+1 Vote

It should be a must !

#29 Updated by Masumitsu Hatta about 5 years ago


#31 Updated by Jan from Planio www.plan.io almost 5 years ago

We've discussed this at Planio at lengths and the verdict was we don't think it's a good idea. It will create large chunks of unstructured text and possibly boilerplate content that cannot be queried against or otherwise be used.

In my opinion, the world should be as structured as possible and we already have custom fields for that: all the questions one would ask in these "issue templates" should actually become custom fields. What's even better: you can make them mandatory, searchable and things will just generally be much better than with templates.

#32 Updated by TridenT Job almost 5 years ago

I would like to use template for my 'backlog' and 'story' bug trackers.
Today, the template is store in a wiki page, and is copy/paste every time.

Template for trackers enables:
  • help the submitter to structure the feedback
  • Give directions, advices to submitter
  • same format for ticket
  • better than custom fields as it is open to any formatted text

#33 Updated by Christian Dähn almost 5 years ago

There are reasons for, but even against custom fields.

E.g. if you have different types of tickets like "service case" and "feature request".

For "service case" the description has to answer some questions, which are EVERYTIME free text answers (what did the customer report? what are possible reasons for the problem? what are the next steps? what is the solution?). When we search for keywords it's not predictable in which of these questions/sections (or: custom fields) these keywords occurr. Therefore we just search the issue description to filter our results - which is efficient for searching, as for creating/editing.

For "feature request" non of the above questions/sections (or: custom fields) can be reused - there are different questions which are entered as free text. So it's very hard to find custom fields, which match all or even most of the description sections of different ticket types.

Further we discussed this topic with our devs and users - with some experiences with issue templates and many custom fields in our previous Trac system. As result the users were happy that they didn't have to face with the big number of form input fields like in Trac (where we splitted our discription into different custom fields) and love the (by url passing filled) description template, where they only have to replace some placeholders with the content.

So: For some cases custom fields is the cleaner and more effective approach, for some cases issue templates do a really better job (covering more than just the description).

Hope this point of view helps a little.


#34 Updated by Fred B over 2 years ago

This can be done in sharepoint when creating project. A project template can be choosed and it create task, user, etc.

In Redmine, this would be particulary usefull to have a template for particular issues, that would auto create sub-tasks and checklists.

This would be a really valueable feature.

#35 Updated by Toshi MARUYAMA over 2 years ago

#36 Updated by Toshi MARUYAMA over 2 years ago

#37 Updated by Toshi MARUYAMA over 2 years ago

#38 Updated by Go MAEDA over 1 year ago

  • Duplicated by Feature #3594: Custom default value of the description field added

#39 Updated by Mateus Demboski over 1 year ago

+1 for a template per tracker and per project

#40 Updated by Mateus Demboski over 1 year ago

I think that this issue can be a good feature to the next 4.0.0 Redmine version, no? =P =)

Also available in: Atom PDF