Our company routinely stands up new websites and follows a series of steps to do so. As a result, we want to create a repeatable template within Jira that someone can follow to be sure they complete all of the necessary steps.
I looked into cloning a "template" project with all of the tasks filled in and ready for completion, but there are two issues with this approach:
Essentially, we want to be able to point at a specific series of steps to be taken to create a website from scratch. It would basically be a checklist.
Is there an easier way to create the same project over and over again each time we need to create a new website?
Hi @lukas , welcome to the community.
It seems to me that you don't want or need an entire new project one standing up websites. Rather I would consider creating maybe an epic with all associated stories/tasks and subtasks. For this I would create a manual automation role that would create all of these issues on demand. You might even decide to do it by uniquely creating the epic as a means of a trigger that would then create all of its children. In this way you can have your unique information about the new website within the epic and the children could inherit aspects of the epic as desired.
If this seems like a reasonable approach there are quite a number of posts within the community about creating recurring tasks using automation. However I am happy to assist in more detail further if this is the direction you would like to go.
@Jack Brickey Thank you for the response! I will dig into this a little further and come back if I need any help. I really appreciate you pointing me in the right direction!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@lukas Welcome to the Atlassian community
Really the way you explained it and creating from CSV are the main options. There is not a clone project function delivered in Jira. So the best two options are:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Brant Schroeder Thank you for the response and confirming my suspicions! I'm going to look more into the CSV route as it seems like a way we may be able to have "templates" for people to use. The only choice they have to make is to pick the right template.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.