We have a couple hundred projects and create a new project every 2-3 days. Each project has the same 5 issue types and each issue type has different fields and layouts assigned to them.
When we create a new project there seems to be no way to automatically apply the issue layouts that we already have in all other projects. Each new project has the fields ordered differently than the existing projects.
Currently we need to use the "copy issue layout to other project" feature but this is not ideal because:
- it seems to be available to Jira administrators only
- it can't be automated through the API
At the moment we need copy the 5 layouts every time we create a new project. Our projects are already created automatically via API and it's very inconvenient that one of our administrators needs to click through the same copy functions several times per week.
Is there any better solution for this?
Thanks!
Hi @Toni August and welcome to the Community!
No, unfortunately not. Copying the layout across projects is the most effective way to share your defined layout across new / other projects.
I wished I could tell you otherwise, but still hope this helps / clarifies!
Hi @Toni August
I think Issue Templates for Jira (developed by the company I work for) can help automate issue creation using predefined structures. This ensures that every new project follows consistent issue type configurations and field setups. Instead of manually copying layouts each time, templates allow you to maintain consistency across projects.
This is a link to the app's Support Center , where you can find more information if you're interested :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Welcome to the community, @Toni August
Hi, I’m Marlene, Product Manager of Deep Clone for Jira.
If you're open to trying an Atlassian Marketplace app, check out Deep Clone. Our app lets any Jira user—not just admins—clone entire Jira projects including their issues. You can choose whether to share existing schemes or create a copy during the cloning process.
You can also control cloning permissions, ensuring that only specific users can clone projects or issues.
You can read more about the Deep Clone Project Clone feature in our documentation.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Did you catch the news at Team ‘25? With Loom, Confluence, Atlassian Intelligence, & even Jira 👀, you won’t have to worry about taking meeting notes again… unless you want to. Join us to explore the beta & discover a new way to boost meeting productivity.
Register today!Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.