How do you clone a ticket set up to a different project?

[Kajol Kataria]

Hi all! I am looking to clone the set up of a ticket to another project. I don't see a clone option, and if there isn't one, is there at least a import + export option? 


Please advise how I can go ahead with moving a ticket set up over! Thanks!

[Trudy Claspill]

Hello @Kajol Kataria 

Welcome to the Atlassian community.

Can you clarify exactly what you mean by the ticket "set up"? Be specific. Are you talking about the content of a specific ticket being copied to a new ticket? Are you talking about the configuration (issue types, available fields, screens, etc.) being copied to another project?

Are you working with Jira Service Management Cloud or Jira Service Management Data Center? If you click on the Help button near your avatar and select About, what do you see for application version information?

What is the Type of the source project? What is the Type of the destination project? Get that information from the Type column on the View All Projects page under the Projects menu.

[Kajol Kataria]

Hi Trudy, thanks for the quick response and warm welcome! Happy to further clarify--

By "ticket set-up," I am talking about the fields that can be added by administrators to Epics, Bigs, Story, and Task set-ups. To clarify, when navigating to the three dots next to a project name >> Project Settings >> Click the Drop-down on Issue Type >> Select an Issue. The page that appears after completing the mentioned steps are what I am referencing. 

I have set up two projects's issue types manually, by adding, editing and creating custom fields. I am wondering if theres a way to clone the set up for different projects. Or even to import/export a issue type set up. 

As per a google search, I see that cloud instances end with ".atlassian.net" and Data Center instances use custom domain names or IP addresses. I think I am using the latter-- Data Center instance. Please advise if this is not the correct way to identify the type of instance I am within. 

The Type of the source project I am working on is Team-managed software. However, we have used Team-managed Business as well. Can you advise which one is more beneficial to use? And does it matter which type of project is used in reference to my question?

Thanks for your help in advance!

[Trudy Claspill]

Hello @Kajol Kataria 

There are a couple of ways to determine if you are using a Data Center instance or a Cloud instance.

1. If you click the Help button near your Avatar and then select About, Jira application information will display. For Data Center you will get an actual version number, like 9.12.4. Jira Cloud does not have a version number.

2. If you view the list of projects, in a Cloud instance the project Types will include labels like Company Managed and Team Managed, which are two types of what I call "project customization architecture". Those labels are not present in Data Center as all the projects there are "classic" (comparable to Company Managed in Jira Cloud).

Since you have noted that your project types are "Team managed", that means you are using Jira Cloud.

On a side note, you have posted your question in the Jira Service Management Questions forum. Jira Service Management is a separate product that enables use of customer support/service desk types of projects in your Jira instance. You noted that you are working with Software and Business types of projects. Those types of projects are part of the Jira product (not Jira Service Management product). There is a separate forum for questions for the Jira product, located here, for future reference.

https://community.atlassian.com/t5/Jira-Software-questions/qa-p/jira-questions

It is not uncommon for community members to post questions about one of the products in the other product's forum.

The Type of the source project I am working on is Team-managed software. However, we have used Team-managed Business as well. 

The configuration of issue types in Team Managed projects cannot be shared with other projects.

The "project customization architecture" (that's my terminology, not Atlassian's) for Team Managed projects is geared to enabling team's to manage the customizations of their project without impacting other projects. The Project Administrators for such projects can create custom issue types, custom fields, and custom workflows. But all of that is localized to the one project, and cannot be shared with other projects.

For Company Managed projects the customizations are managed by Jira Administrators and can be shared between Company Managed projects.

As long as you use Team Managed projects you will have to manually recreate all those configurations in each TM project that you create. There are no native features to clone, export, or share those configurations with other projects.

If you can instead use Company Managed projects, then the configurations can be shared between projects.

You can find more information about the differences between Company Managed and Team Managed projects here:

https://support.atlassian.com/jira-software-cloud/docs/learn-the-basics-of-team-managed-projects/

You did not mention what your level of access is in the Jira instance. When you click on the gear icon near your avatar in the upper right corner of the Jira screens, what options do you see? Do you see options like System, Products, and Issues? If you do, then you have Jira Administrator access. If you do not, then you don't have Jira Administrator access.

If you don't have Jira Administrator access, you will not be able to create Company Managed projects and you won't be create the configuration elements that can be shared, nor will you be able to create Company Managed projects.

While "Company Managed" and "Team Managed" specify how customizations are managed, the other aspect to Project Types are Business and Software (in the Jira product). These types of projects provide different base templates (covering issue types, workflows, and screens) as well as some differences in core functionality. For example Business projects provide only one type of Board view for the project content, and don't support a board Backlog. Software projects support having multiple Board views, using Scrum and/or Kanban board views, and have board Backlogs. 

Deciding which one is the best for your team depends on the functionality you need for managing your work.

[Trudy Claspill]

Hello @Kajol Kataria 

Did my responses adequately address your questions? If so, please consider clicking on the Accept Answer button to mark your Question as Solved.

If you still have outstanding questions about this topic, let us know.