Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Can I copy/clone settings from a current project into a new project in Jira Software?

I've been asked to create a new project, using the settings/issue templates/etc. from an existing project. I'm seeing a lot of how-tos on how to do this in different versions of Jira; but is there any way to do it in Jira Software?

1 answer

1 accepted

0 votes
Answer accepted

Hi @Daniel_Oborne 

You can create a new project, sharing a range of settings with an existing one:

  1. In Jira, go to Projects > Create Project
  2. Check the box "Share settings with an existing project"
  3. Continue on to create the project

^ This will re-use the existing schemes on a new project. This doesn't clone/create new ones - it just means the new and existing projects will share common workflows, issue types, screens, fields, permissions, notifications, etc.

See more information on Shared Configuration on this page.

Note: This is for Classic projects only. It is currently not possible to share schemes across Next-Gen projects.


Thank you. I've been told that the share settings option is available, but while trying to do this for a Next-Gen project, I haven't been seeing it.

Hi @Daniel_Oborne 

Yeah - it's not available in Next-Gen at this stage, as each project and its configuration is designed to be entirely independent from all others. 

There is a feature request to allow this though - check-out JSWCLOUD-17430 


Like # people like this

I have to say I get increasingly frustrated with these "nope, can't do that on a next-gen project" scenarios for something that should be an obvious default feature. When will Atlassian begin paying me for the time it takes to recreate settings that could have been saved with the option that was available in the OLDER version?

Suggest an answer

Log in or Sign up to answer
Site Admin
Community showcase
Published in Confluence

Introducing External Collaboration for Confluence

We’re excited to introduce external collaboration for Confluence, now available in early access. It is available to preview for Confluence Cloud Premium and Enterprise customers. (If you're not on ...

237 views 0 8
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you