Jira Work Management vs Asana

[Tayla King]

Has anyone found a way to easily duplicate recurring projects in JWM as you can in Asana (without being a system admin)

For example, if I want to duplicate an entire project (that we know will be recurring many times throughout the year) with tasks and dependencies, is it possible? 

I have not found an easy way to do this as of yet 

[Dave Meyer]

Hi @Tayla King I lead the Jira team. Hopefully this doesn't discourage others from suggesting ways to accomplish this, but these types of repeated processes are something we're looking at investing in to make easier in the near future. Feel free to email me dmeyer (at) atlassian.com and I can connect you with a member of our team soon to understand your needs.

[John Funk]

Hi Tayla - Welcome to the Atlassian Community!

Yes, as Dave mentioned, can you share the exactly scenario of what you are doing to accomplish by the "duplicate projects"? Just thinking that this might be accomplished through Epics as your "project" instead of the actual project level itself. The other way might be to duplicate the project by creating a project based on an existing project. And then using automation to create your initial set up tasks/issues. Or finally, using an add-on like the Revyz Data Manager for Jira tool to clone a template project and a set of issues. 

[Mark J Cunningham]

For Projects

Create the various configuration templates, then via API you can create project from those configs

For Tickets

For Playbooks (ie set of stuff for each project/release), we use a product called Deep Clone

You can prefix and change parts of the name and link it to a new Epic at clone stage, as set the target project

you need to have some way to filter the template, and then run deep clone off of that filter