Does "Clone" also clone the status?

[Jim Strange]

As per the title: If I clone a ticket, does the clone also inherit the status from the source ticket?

[Julien Peyrade _ Elements]

Hello @Jim Strange 

If you don't mind using a add-on, Elements Copy & Sync lets you copy issues and initialize them with the status of your choosing.

Full disclosure, I'm the Product Manager of the app.

Basically, with our app you can :

• initialize an issue with the exact same status as the original issue
• initialize an issue with any status, depending on the status of the original issue
• even if the status don't have the same name
• even if the two issues are not in the same project
• even if the two issues don't share a workflow
• no matter the validators and conditions on the workflow

(You can even keep the status of the two issues synchronized if you need to, it's completely optional.)

To do this, you just have to configure a status mapping once, and enable an "Apply on issue creation" option : 

The app is free for 30 days, (and stays free if your instance is under 10 users), so feel free to give it a try, and don't hesitate to tell reach our Support if you have any question.

Kind regards,

Julien

[Marlene Kegel - codefortynine]

If you want to clone the issue status, you could try our app Deep Clone for Jira.

Don't hesitate to get in touch with us, if you have questions or feedback.

[CAO Ngoc Tan]

Hello,

I did try to clone all tickets from a service project to a software but the status all gone. The option ticket status was checked.

May be Deep clone doesn't support between different project type ?

Br,

Tan Cao

[Marlene Kegel - codefortynine]

Hello @CAO Ngoc Tan,

I am sorry that you experienced an issue while working with Deep Clone for Jira.

It is possible to clone the issue status between different project types with our Jira cloud app.

I'll add some info that might help you troubleshoot the issue. If the issue persists, please reach out to our support team. They will definitely be able to help you with your case.

To clone the issue status, the workflow of the target project must meet the following requirements:

• A status with the same name must be available in the workflow of the target project.

• The workflow must have a transition from the initial status to the status that should be cloned.

• The transition to the status must not have required fields.

• There shouldn’t be other workflow conditions or validators that prevent a transition from the initial status.

When Deep Clone clones an issue it creates the issue (with the initial status (e.g. open)) and transitions the issue after it was created. If you want to clone the issue status "done" but it is not possible to transition from "open" to "done", Deep Clone is not able to clone the issue status. 

[Maciej Opala]

Hello,

you can find one of our (disclaimer) apps useful: Clone Epic Template

It can be used to clone epics together with (optionally) all their issues and sub-tasks. It supports almost all native Jira fields and majority of custom fields.

Best regards,
Maciej Opala from HeroCoders 

[Fabian Lim]

Hi @Jim Strange

It doesn't. Here is more info: https://www.tutorialspoint.com/jira/jira_clone_an_issue.htm

[John Funk]

Hi Jim, no it places the new issue that is created in the first status of the workflow. Usually that’s the backlog.