Issue Details (XML | Word | Printable)

Key: JRA-5179
Type: Improvement Improvement
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: Ruben F. Valdez
Votes: 11
Watchers: 4
Operations

If you were logged in you would be able to see more operations.
JIRA

Add Template Functionality.

Created: 09/Nov/04 02:16 PM   Updated: 28/Feb/08 08:00 AM
Component/s: Issue Fields, UI / Usability
Affects Version/s: None
Fix Version/s: None

Time Tracking:
Not Specified

Issue Links:
Duplicate
 

Participants: Didier Lévesque, Justin Callison, Peter Tillemans, Ruben F. Valdez, Ryan, Scott Farquhar [Atlassian] and Todd Patterson
Since last comment: 31 weeks, 5 days ago
Labels:


 Description  « Hide
It would be nice if you could create templates with certain field already populated with specific data.

 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Scott Farquhar [Atlassian] added a comment - 09/Nov/04 03:29 PM
Ruben,

Can you outline what templates you are talking about?


Ruben F. Valdez added a comment - 10/Nov/04 06:43 AM
For me it would be for creating new issues. If I could set up a template so as to when I selected Create New Issue, I got a list of templates to select or navigate to my templates and create a new issue from a template. When doing this certain fields would be pre-populated such as "Assign To" and "Affects Version/s". Where I work all issues that we open go to our manager and we work on one version of code for a certain period of time. It would be nice not to have to select this information everytime, especially when you are creating several issues at one time.

Thanks!


Didier Lévesque added a comment - 06/Nov/07 07:32 AM
I would be nice for me too. What I would like is to have a way to put a template in the description... So all the issues will get all the same structure.

Ryan added a comment - 26/Nov/07 02:43 PM
I estimate that this would save me about 30 seconds for every JIRA task I enter. Multiply that by the number of tasks entered, and number of users who don't use the default options, and this change results in a significant productivity gain across the company

Todd Patterson added a comment - 26/Dec/07 02:58 PM
I just voted for this issue.

Adding this functionality would increase efficiency for our Engineers tremendously; I can't tell you how many times users have asked me to "pre-populate" the description field with our default template (rather than copy-n-paste the template).


Justin Callison added a comment - 17/Jan/08 05:09 PM
I would like to see this as well. In the meantime, you can create a bookmark that contains something like the following, which will populate the Description field:

javascript:(function(){myString="Story:\nAs a <ROLE>, I would like to <>.\n\nAcceptance Criteria:\n1. First Criteria\n2. Second\n";ta=document.jiraform;document.jiraform.description.value=myString})()

Add that to the toolbar in firefox and you can populate it with a click. Not ideal, but it's better than typing ....


Peter Tillemans added a comment - 28/Feb/08 07:58 AM
We are using Jira to support our processes.

This would be ideal for e.g. 'Standard Changes' .

It's got my vote!


Peter Tillemans added a comment - 28/Feb/08 08:00 AM
The open source Scarab issuetracker has a nice implementation for it.