Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

How can I duplicate a project with the same tasks outside of manually importing tasks?

Trevor Overstreet
Contributor
August 30, 2022

For our client onboarding process we have an employee who has a set list of tasks to complete for every client. The tasks are generally the same for every client.

I need an easy way to duplicate a project board with tasks for every new client this employee onboards.

Ideally, it would be nice to have a parent project for this employee and sub projects under the parent with the same tasks for each client so we don't have 50+ new projects created in 6 months, etc. If this is possible I also need SLA's for each client that is onboarded.

Any advice is appreciated! Thank you!

1 answer

1 vote
Mark Segall
Community Champion
August 30, 2022

Hi @Trevor Overstreet - If you have repeatable steps that occur for each client, then yes a single project makes sense.  It eliminates a lot of overhead in having to create and archive projects over time.

You can go about this a few ways, but to better understand which is the best approach, can you provide a little more information on a couple things?

  • How many repeatable tasks are we talking about?  If it's a relatively small number, this can likely be achieved with automation
  • Are these tasks also broken into sub-tasks?
  • For SLAs, are you looking for actual SLA tracking or simply pre-populating a Due Date based upon date created? If the former, Jira Service Management makes sense, if not, you could save some licensing and go with a simple Work Management project.
Trevor Overstreet
Contributor
August 31, 2022

Hi and thank you for the quick reply Mark!

-The repeatable task is around 42. (I tested the external system import function which works fine but again we'll have many projects overtime)

-Yes, there are sub-tasks and the total count includes the sub-tasks

-Good question. I don't think it would make sense to use SLA's like you would for customer service intake on each issue since these are simply daily tasks, however, if JSM is the best option then I'll make it work. We do have JSM and Work Mgmt so whichever option is best I'll build it.

(I did build a test project in Work Mgmt but do not see SLA's and also curious how to go about re-using the same "list template" in the same project vs. re-creating over and over archiving old projects)

 

Hope the above gives more insight!

Mark Segall
Community Champion
August 31, 2022

The 42 issue count puts this on the edge of using automation, but you could try something similar to what I posted here for the short term:

https://community.atlassian.com/t5/Jira-Software-questions/clone-an-epic-including-its-child-issues/qaq-p/2091431

However, given that number and supporting possible need to scale the number of tasks, I would recommend investing in a marketplace app like Bulk Clone or Deep Clone

Trevor Overstreet
Contributor
August 31, 2022

I will take a look at the above article. Do you suggest I create a software development kanban project/template and use Epic/ stories for each "client" with corresponding repeatable tasks?

Or which template would you suggest I use? (even if I do purchase bulk Clone or Deep clone)

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events