What is the best practice for creating a repeating set of tasks


Our process for launching a new customer involves (Largely) the same tasks/steps.  I'm looking for the best practice for tracking this in JIRA.  I'm thinking some kind of template or cloning of a project so I don't have to create the same 20-30 tasks every time.  Can someone share what they have found to be the most effective?



1 answer

Probably not much help, we didn't find anything out there so we created a post-function with parameters [project, issuetype, task name that concatenates with parent name] to create sub-tasks in a transition. (We already had an add-on of our own with some other functions.)

Suggest an answer

Log in or Join to answer
Community showcase
Emilee Spencer
Published yesterday in Marketplace Apps

Marketplace Spotlight: DeepAffects

Hello Atlassian Community! My name is Emilee, and I’m a Product Marketing Manager for the Marketplace team. Starting with this post, I'm kicking off a monthly series of Spotlights to highlight Ma...

41 views 0 3
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