So naturally it's the cloning part of your question that piqued my interest — I'm always keen to understand what people need from advanced cloning and where Jira's built-in capabilities hit their limits.
Before diving into cloning, it's worth noting that
@Aaron Pavez _ServiceRocket_ raised some valid points in his response about alternatives to cloning that may be worth evaluating.
That said, there are scenarios where cloning is a legitimate and practical choice — so let me walk through your questions from a cloning point of view.
1. Is this approach recommended in JSM for SLA/compliance management?
While Jira Service Management typically encourages keeping a single ticket for its entire lifecycle, your approach is a valid workaround for compliance and reporting when "Time to Resolution" metrics are strictly audited. By closing the original ticket and creating a linked clone, you can "stop the clock" for reporting purposes while maintaining the operational context in the new ticket.
2. Can ticket cloning be automated based on ticket age, SLA threshold, or status conditions?
Yes, this can be automated. Jira Automation supports scheduled triggers (e.g., a rule that runs daily and checks for tickets older than X days) and SLA breach triggers that fire when a specific SLA metric is about to breach. You can combine these with a clone action.
However, Jira's native clone function is very limited — it essentially copies the summary and description, but does not carry over comments, attachments, custom field values, issue links, or subtask structures. For a compliance workflow where the cloned ticket needs the full context of the original, the native clone will leave you with a near-empty ticket that requires significant manual rework.
3. Is this achievable through native Jira automation, or are marketplace apps required?
As just mentioned: native automation can trigger a clone, but the result is too bare-bones for most real-world compliance use cases.
I would recommend using a Marketplace app instead, such as our Deep Clone for Jira app. Deep Clone supports full-depth cloning including comments, attachments, custom fields, issue links, and subtasks. It integrates with Jira Automation, so you can trigger deep clones automatically based on SLA thresholds or scheduled rules. And you can create Cloning Presets to define exactly what gets copied, making the process repeatable and auditable.
4. How can we maintain traceability between the original and cloned tickets?
When cloning via Jira Automation, you can add the "clones / is cloned by" issue link by adding an action to your automation rule and thus maintain traceability.
Our
Deep Clone for Jira app handles this regardless of how you trigger the clone — whether manually, via post-function, or through Jira Automation. In addition, it offers more advanced tracing options such as:
- Automatically adding custom comments to both tickets explaining the reference and providing background information.
- Prefixing the summary of the new ticket (e.g., "FOLLOW-UP: [Original Summary]") to make it clear in reports.
- Using dedicated labels.
5. Best practices and alternative approaches
As mentioned above, cloning is not the only way to handle SLA compliance in JSM — there are other options worth evaluating before committing to a cloning workflow.
If you decide that cloning is the right approach for your setup, here are a few tips to keep it clean:
- Use Cloning Presets: In Deep Clone for Jira, you can define presets that ensure every clone — whether triggered manually or via automation — follows the exact same rules (which fields to copy, which status to start in, etc.).
- Keep the customer in the loop: Use Jira Automation to notify the customer when a new ticket has been created for their request. Transparency here avoids confusion and support overhead.
If you have questions about advanced cloning functions using
Deep Clone for Jira - feel free to reach out.
Best,
Evelin
codefortynine
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.