How to automate creation of repeated tasks in new sprints

We've got some analysis work that needs to happen with each sprint in our project. We're looking at weekly sprints, so manually creating the same tickets every single time sucks (and is at risk of getting missed/forgotten).

Is there a way to automatically generate a set of tickets on the creation of each sprint?

3 answers

Issue Templates is indeed cool, but it creates only one issue (and its subtasks) at a time. You can automate issue creation for several parent-level issues in workflow post-functions, but that's not quite what you need.

A nice free solution is Quick Subtasks, which creates a bunch of subtasks from a template. 

I think the most efficient would be Clone+, where you could have a batch of parent-level issues that act as your default stories (just leave them in a future sprint you never start) and mass-clone them when you start your sprint.

That being said, it's a bit unusual to have recurring tasks like this in a sprint. If what you have is recurring Subtasks (like, each story has an analysis subtask), then Issue Templates or Quick Subtasks would work fine. Maybe you could tell us a bit more about your setup?

I will vote +1 on the Clone smile

I may use this approach. Our use-case is probably atypical of most JIRA users. We're a analytics department in an agency, and our work with clients is on a weekly cadence. We have tasks that are repeated with weekly data updates (i.e. data integrity and validation work), then we have one-off and ad-hoc investigations that get slotted into our workflow. We have regular client-facing work that goes out in various cadences as well. We're not developers but we do follow agile processes for our weekly work. Our weekly data validation and weekly reporting is what I want to have automatically created with every sprint.


If I create this sprint "template" that never launches, can I just clone the sprint with everything inside it?

You can't clone a sprint. You can't create a sprint through the API either, so the scripted solution is out I guess.

You could always do a blitz and prepare several sprints in advance. Manually create all the sprints for the coming month, do a bunch of clones, and forget about it for a whole month.

That gets pretty close to just doing standard issue cloning and throwing into sprints though... so it doesn't sound like that much of an advantage over default functionality.

The advantage is that you clone the issues in bulk rather than one at a time. The gains are greater the more issues you have. 

You have an option to create "Issue Templates" and just clone them to re-use them. You may also want to take a look at JIRA Issue Templates (

Cool, I'll read up on this.

This is cool. I suppose I could adapt it to create the actual sprint, then throw the default tasks inside the sprint - right?

What you do in the privacy of your own server is up to you wink.

Suggest an answer

Log in or Join to answer
Community showcase
Teodora [Botron]
Published Thursday in Marketplace Apps

Jira Inferno: The Nine Circles of Jira Administration Hell

If you spend enough time as a Jira admin - whether you are managing a single, mid-sized instance, a large enterprise one or juggling multiple instances at once - you will eventually find yourself in ...

394 views 1 13
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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot