You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
We have the following requirement. We want to export an issue type from Project A and import it back into project B. We wanted to have the same issue type from project A across couple of projects. Out of the box, I dont see a way to do it. I see there is a plugin "project configurator for Jira". Not sure if the plugin helps with my requirement
Is there a way we can export and import an issue type as per my requirement.
Hello @Santhosh Solipuram ! Welcome to the Atlassian Community!
Are the projects on the same Jira Cloud instance? If they are, issue types used in projects are associated through the Issue Type Scheme. You need to see if Project A and Project B use the same Issue Type Scheme or that the Issue type you want is in the Issue Type Schemes associated with each Project.
Not for team-managed projects. It's far easier to have common issue types across projects using schemes on company-managed projects.
Hello @Santhosh Solipuram
Welcome to the Atlassian community.
Are you working with an issue type in a Company Managed project or a Team Managed project?
What exactly do you expect to be carried over in that export/import process?
Hello @Santhosh Solipuram
Into what type of project to you want to import the issue type?
And exactly what are you hoping to carry across during that import? The fields associated with the issue type? The screen layout? The workflow?
The short answer is I don't believe there is any way to "export" an issue type and its associated configuration from a Team Managed project and import that to another project.
You have to recreate the issue type and associated configurations in the destination project.
The configurations of Team Managed projects are specifically not intended to be shared. The concept behind Team Managed projects is to be able to customize a project completely independently without impact to other projects.
Company Managed projects, on the other hand, leverage configurations that can be shared. You can define Issue Types globally that can be organized into Issue Type Schemes that can then be assigned to projects, for example.