Jira Project Cloning ticket of that project has different options then another project.

[Micheal Lett]

Hello,

I am having an issue with two Projects, they are under Service projects but when we go to clone a ticket from one of those projects, we get no included options. Our other projects are Software projects and when we clone a ticket, these have included options such as comments, attachments and sprint values that we can select. Field for report and assignee is also missing when comparing to other projects. 

(Yes, the ticket I am trying to clone has comments or an attachment for testing) 

[Trudy Claspill · Accepted solution]

Hello @Micheal Lett 

Welcome to the Atlassian community.

Based on my experimentation using the Clone option for an issue in a Service Management project does not include the option to clone the comments.

I have not found an issue documented for this in the Atlassian public backlog.

Nor did I find issues for the absence of Reporter and Assignee.

If you would like to submit change requests to get those added you can work with your administrators to open a support case directly with Atlassian, or you can provide that feedback to them by clicking on the Help button in Jira (near your avatar) and using the Feedback option therein.

[Bogna Krystian_Deviniti_]

Hi @Micheal Lett 

If you're interested in Marketplace add-ons, I think Issue Templates for Jira (developed by the company I work for) is worth considering, given your use case.

It can help by allowing you to define cloning templates that include specific fields, comments, and attachments when creating new issues. This ensures that cloned issues retain necessary information across various project types, including Service projects.

This is a link to the app's Support Center where you can find the app's demo, documentation and more information

[Marlene Kegel - codefortynine]

Welcome to the community, @Micheal Lett.

Hi, I’m Marlene, Product Manager of Deep Clone for Jira.

If you need to clone JSM tickets, including their comments, Deep Clone can help. It also allows you to move tickets to other projects during cloning—for example, when escalating them to second-line support.

To make the process simpler and reduce errors (such as missing field selections), cloning can be triggered automatically during a workflow transition or via a button in the issue action menu.

More details on ticket escalation with Deep Clone for Jira can be found in our documentation.