What is the best way to create issue templates (pre-defined set of stories/sub-tasks that can be reused) in Jira?


we are trying to maximize efficiency when entering the stories and sub-tasks in Jira. And currently, we have several stories that follow the same "recipe". Imagine a website project for example, we have several pages (as stories) and then the subtasks are always the same: UX, Content, Design, Build, etc..

How can we speed this process up, by creating templates that we can easily add to any project?

I don't know if it helps, buy we are using Structure - an awesome plugin for Jira.

Thank you!

1 answer

Not sure if this is exactly what you were looking for, but cloning an issue worked for me in the past except that JIRA Agile would copy the 'master' story's sprint value -which I didn't want. This just changed in a JIRA update and might be helpful if I'm understanding your request: https://jira.atlassian.com/browse/JSW-6541.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,718 views 17 21
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you