Jira ticket cloning

[VanshikaG]

I am working as a PMO for a Managed Services team, where the complete operational workflow is handled through Jira Service Management (JSM). Tickets are created, assigned, worked upon, and resolved within the platform.

However, in some cases, tickets remain open for extended periods due to dependencies such as awaiting customer inputs, approvals, third-party responses, or long troubleshooting timelines. From a compliance and operational reporting perspective, we aim to ensure that tickets do not remain open beyond a 7-day window.

To address this, I would like to understand whether Jira ticket cloning can be implemented for tickets that exceed the defined timeline. The objective is to close the original ticket within the compliance window while automatically creating a cloned/linked ticket that carries forward the pending work and context.

I would appreciate guidance on the following:

• Is this approach recommended in JSM for SLA/compliance management?

• Can ticket cloning be automated based on ticket age, SLA threshold, or status conditions?

• Is this achievable through native Jira automation, workflows, or would marketplace apps/plugins be required?

• How can we maintain traceability between the original and cloned tickets for reporting and audit purposes?

• Are there any best practices or alternative approaches commonly used for such scenarios?

Looking forward to suggestions and recommendations from the community.

[Aaron Pavez _ServiceRocket_]

Hi @VanshikaG 

Ill suggest to take a look at ITIL for best practices. Good place to start.

> Is this approach recommended in JSM for SLA/compliance management?

its not for several reasons. reports, customer sentiment (too many tickets), the audit gets confusing (5 tickets opened for the same issue with no resolution and keeps piling)

The cloning part is the not so good/best practice. closing the ticket when the SLA says so , yes.

> Can ticket cloning be automated based on ticket age, SLA threshold, or status conditions?

yes you can. Jira automation is limited on what it can copy/clone. 

https://support.atlassian.com/jira-software-cloud/docs/clone-an-issue/

> Is this achievable through native Jira automation, workflows, or would marketplace apps/plugins be required?

Automation, limited. best use a 3rd party app.

https://community.atlassian.com/forums/App-Central-articles/The-Complete-Guide-to-Cloning-in-JIRA-in-2026-How-to-Clone-Work/ba-p/3013253

> How can we maintain traceability between the original and cloned tickets for reporting and audit purposes?

If you want to go this route, its either a label or a link.

> Are there any best practices or alternative approaches commonly used for such scenarios?

move the ticket to another work type with a longer SLA.

train people to work on the work items and reply accordingly.

chase customers for reply.

Regards

[VanshikaG]

Thanks for your inputs. I will explore more around this. 

[Olga Cheban _TitanApps_]

hi @VanshikaG !
Welcome to the community!

As Aaron mentioned earlier, the cloning approach has its drawbacks. As you also asked for best practices, here's what I can share.

A common approach is to close tickets automatically after a period of inactivity and then reopen them automatically if the user replies. Before the ticket is closed, the automation rule can add a comment notifying the user that the ticket will be closed unless they provide their input. This can be done with native Automation for Jira.

For a detailed rule scheme and other best practices, you can take a look at my article 10 Jira Service Management Automation Rules That Every Team Should Use.

I hope this helps!