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

How to copy my customize issue type to another next-gen project


I add one new issue type in project setting,and I want use that in another project,how can I copy that new issue type to new project?

3 answers

1 accepted

0 votes
Answer accepted
Ollie Guan Community Leader Oct 31, 2019

Hello @ikeli ,

Share next-gen project configurations and workflows Coming in 2020.

For teams that want to share next-gen project configurations and best practices, you’ll be able to copy a project, including custom issue types and workflows. Projects will continue to remain independent after you copy them. This will be particularly helpful for teams that want to share next-gen best practices across teams.

@Ollie Guan 

Is there any update on the timeline for this feature?

This would be really helpful for our team!

Ollie Guan Community Leader Mar 24, 2020

No new progress, still waiting for release.


Like Thomas Brown likes this

Hi @Ollie Guan ,

That is very broad timeline "coming in 2020".

Can you share a little bit more details?

Like Christian Giroux likes this

Adding a +1 to the questions over clarification on timeline. 

I also don't think the accepted answer is actually relevant to the use case, unless I'm misreading. We maintain 40+ next gen projects and routinely have to roll out a new org-wide issue type manually across all of these projects, which is heinously manual. It sounds like the feature in the works is more designed to clone a project to create a new one. Is that not correct?

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Team-managed projects

4 steps to get actual statuses on the Jira board.

Jira   is a powerful tool   that helps teams to plan, manage, and report on their work.   We love using Jira, especially for its ability to track issue progress. But how to monitor the...

1,199 views 10 14
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