How can I create an User Story template in Jira?

[Sebastian_Grutz]

We have specific project in Jira. If we create an User Story we have a template how to write it. Is it possible to generate this template in Jira, so when we create a new user story in this project the template is already there?

[Christine Stolz]

So I am working ways to improve the process with the team (using Agile in a Waterfall world, so I am adapting).  One of the things that I have thought of is to:

1. Create a generic user story with associated sub-tasks, etc. for a standard development.

• As a [role], I would like to do [task], in order to do [objective].
  • Subtasks - 
    • Analysis
    • Development
    • Code Review - [4 hour estimate in general]
    • Merge - [1 hour estimate in general]
    • Etc.

2. Every time there is a new user story needed, take a clone of the generic user story and work on it that way.

3. Take the cloned user story and customize it to the work at hand.

• As a Basketweaver, I would like to design my baskets with CAD, in order to mass produce.
  • Subtasks - 
    • Analysis - Basketweaver CAD specs [4 hours]
    • Development - Basketweaver CAD dev [10 hours]
    • Code Review - [2 hour]
    • Merge - [1 hour]
    • etc.

Not sure that is advisable. 

Any thoughts or suggestions?

[Jon Mills]

Sounds perfectly reasonable to me if not using a plug-in. I'm looking at doing exactly this.  The subtask names will all come prefixed with CLONE (by default but can be disabled on a global instance basis)

[Jim Coryat]

We are doing the same thing.  Given the tool this seems to be the path of least resistance.

[Conrad Bruchmann]

Simply go to Project settings-> Automation

Here you can insert a template text into the description. Works fine for me.

[Norah Medlin]

Thank you for reminding me about this!  Jira Automations are VERY powerful!

[Muhammad Khan]

Yes though Project Settings > Issue Types > Story > Description (type in text you want as a template) > Save Changes.

Now create a new story to see if template text is included. 

[sam2095]

What version / type of Jira are you using?  I don't seem to have the option to edit the Description.  Thanks, Sam.

[Jeremy Chambers]

ditto, i don't see this capability in Cloud Jira.

[Muhammad Khan]

I am using Cloud JirA too.

[laurilarjo]

I cracked this mystery!

You can indeed create description templates as Muhammad showed, BUT your project needs to be "team-managed project" (aka next-gen). By default the projects are "company-managed" (aka classic). You can google for how to do a migration, Atlassian has an article about it.

[Lucy Dilts]

Have to agree w/ James. This is a basic feature of every PM tool our teams have used in the past.

[Sari Ollikainen]

Is this again a feature, which does not exist in Jira?

[Leon]

I would simply create a story with all template contents needed,

Then, I'll ask all teammates to create new story by cloning the story.

This way doesn't require any plugin.

[Jim Coryat]

But requires teammates to perform an additional manual step.  This makes is NOT the path of lease resistance which then equates to being optional and processes break down if the team is not motivated to comply.  This is a major gap in the features of the product.

[Pavel Pavlovsky]

Hey @Sebastian_Grutz ,

You can try Easy Templates for Jira Issues add-on: https://marketplace.atlassian.com/apps/1219112/easy-templates-for-jira-issues

It allows you to create the most general and useful templates for different issue types and cases, like story, bug report, on/offboarding and other processes. Add subtasks and set Templates per issue type.

Cheers,
Pavel 

[Alexey Matveev _Appfire_]

Hello,

Kindly, have a look at this plugin:

https://marketplace.atlassian.com/apps/1211044/issue-templates-for-jira?hosting=cloud&tab=overview

It is not possible to have issue templates out of the box.

[Sebastian_Grutz]

Hi Alexey,

thank you very much for your help!

Best regards

[Alexey Matveev _Appfire_]

You are most welcome!

[James Klein - Deactivated]

sorry but that's totally garbage. Why would we need to pay for a feature that comes out of the box in every other project management tool, including the free ones, on the market?