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

Hello,

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?

Thanks,

Jerry

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 Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published yesterday in Jira

5 ways you can make the most of Jira Software and Bitbucket Cloud

As part of the Bitbucket product team I'm always interested in better understanding what kind of impact the use of our tools have on the way you work. In a recent study we conducted of software devel...

42 views 0 4
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