|
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! 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.
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
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). 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 .... We are using Jira to support our processes.
This would be ideal for e.g. 'Standard Changes' . It's got my vote! The open source Scarab issuetracker has a nice implementation for it.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Can you outline what templates you are talking about?