nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Creating sub tasks based on templates

Leo Catallo

Oftentimes I find myself in need of creating a story and a set of standard subtasks like "Write SRS section", "Peer review design", "Create unit tests", "Run integration tests", "Create story report", etc

I would very appreaciate a feature that would allow me to pick a story template and automatically create the subtasks.

I found this old issue where a solution is offered to exact same question: https://answers.atlassian.com/questions/25049/jira-creating-sub-tasks-automatically-based-on-a-template

However that one was almost 2 years ago, I bet Jira had gotten better since.

Which is the best way to auto-populate story with subtasks?

Accepted answers

Leo Catallo

And I have finally found a plugin that does exactly what I need:

https://marketplace.atlassian.com/plugins/com.hascode.plugin.jira-quick-subtasks

Simple and straightforward, minumum intrusion. Highly recommended.

All comments

Bob Swift

Consider using Create On Transition for JIRA.

Leo Catallo

I think you've posted the wrong link - it leads to "What happened to..." page

Fabrizio Galletti

This is the link

https://marketplace.atlassian.com/plugins/org.swift.jira.cot

it's really a nice plugin, all of that could be done with scripting (with script runner) but that plugin helps administrators and it's well made.

Bob Swift

Thanks for pointing that out. I copied a really old link. It is updated now.

Leo Catallo

In case if someone else is searching, another way I found useful is creating a model task with subtasks and cloning it each time you are creating a new task you need templated.

Leo Catallo

Frankly, this https://dq1dnt4af4eyy.cloudfront.net/files/org.swift.jira.cot/screenshots/96dfd834-1384-4317-a11d-4cf407ca71d5.png

looks really intimidating. Maybe, I'll try it, though

Bob Swift

Yes, it can be . Just use the minimum you need for your use case and know that there are some more advanced capabilities when the need arises.

Leo Catallo

And I have finally found a plugin that does exactly what I need:

https://marketplace.atlassian.com/plugins/com.hascode.plugin.jira-quick-subtasks

Simple and straightforward, minumum intrusion. Highly recommended.

Nicole Downes

For those of you that cannot/not permitted to have all the suggested plug-ins, the simplest way is to construct an import file in excel in csv format and import the file. I have used this many times to create the epics, stories and sub-tasks all at the same time. You can include assignee, estimates, story points, description and whatever else you need in the file. Only restriction is to create linked items (such as sub-tasks), you need to be a system administrator to have import permission.

I keep the file in Confluence. Then I use excel's file and replace to change the epic names and other information that may be project, client, or environment specific.

This solution is not as fancy as others, but it gets the job done.

https://confluence.atlassian.com/adminjiracloud/importing-data-from-csv-776636762.html

George Psistakis

Hi @Nicole Downes love it! Do you happen to have an Excel you can share. It will save ages to me so thanks in advance for that.

Nicole Downes

Can't find a place to load a file, so here is a screen shoot. Give me your email address and I will happily send you the file.

Important tips:

Assignee must match jira username.
Estimates are in Seconds.
Issue ID number is important for linking with the Parent ID. It doesn't matter if you already have issues in your project, you can start at no. 1 in the import file and jira will assign the correct new project key number when it imports.
Summary can be only a single line. No returns. Summary MUST be included in the file for each issue. This is the only mandatory field.
Description can include multiple lines if needed.
You must be system administrator to import sub-tasks!!!!
If under 250 lines you can use - Issues > Import issues from CSV. Use this as it can validate the file for you before you import
The - Issues > Import issues from CSV does NOT allow the Status to be imported. However it can be imported using - System > External system import. If not included, each issue is created with the first status in the workflow for that issue type.

George Psistakis

thank you so much for the head start. I got the idea I will start working on my own.

Thanks for all the tips too

Mark Francisco

Hi @Nicole Downes - Is this method applicable for JIRA Server of for JIRA Cloud only?

Can you please send me the sample excel/csv file please at <markalvin.francisco@safeway.com>. Thank you.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-administration

task

sub-task