Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Copy project with no data

How can I copy an existing custom project such that it does not include the data and I will allow me to modify screens, workflow, notifications and anything else custom,  without changing the project that it was copied from. 

I've used the 'Built-in-scripts' to copy a project, but the resulting project appears to be 'sharing' the same workflow, scheme and screens.   

I want to start with one project to save time, and then modify the new project to slightly different specifications. 


2 answers

0 votes
Daniel Ebers
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Jun 04, 2021

Hi @Madeline Asmus

what you described is the advantage many admins see from copying a project using "Built-In Script" to keep a clean, tidy and uncluttered Jira instance by having as less as possible diverging configuration.

However, your use case indeed can be valid - you would just need to use 'stock' Jira feature to create a new project.

Doing so, new configuration is created, that is mainly not shared (except for a few things like Permission Scheme, for example). So you are more flexible by doing so. If you want to share a single element (like a workflow) you could still do it.

I agree, when using Built-In Script you would have to create new configuration and assign it one by one to the new project which could take more time in this case than to use the 'stock' feature.


0 votes
Alexander Bondarev
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 27, 2021

Hi, @Madeline Asmus !

Welcome to the Community!

As I know it is impossible to do out-of-box. And I believe that it is cool feature and great practice to re-use schemes. 

But I get your case - try to search external apps, for example, ScriptRunner for Jira can copy projects with Built-in-Scripts.

Hello Alex,

I did use Scriptrunner and my question is did it give me a project that is sharing the original projects screens/schema/fields,  because it sure does looks like it. 

If I I tailor the new project - it looks like I would be changing the original project. 

Is there a way to copy the project so it doesn't share, but makes it's own instance. 

It seems like this would be a common practice.  I've worked with Oracle databases for well over 10 years,  and it's frustrating for me not having the dba access to look under the hood at what is provided.    



Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events