Menu
Escalate issues #Elements Copy & Sync

Escalate issues to teams in different Jira projects using Elements Copy & Sync

Use case benefits

An efficient way to clone and move issues from Jira Service Management to your Jira Software project

Clone and move between Jira Service Management and Jira Software

Configure automatic escalation of issues from JSM to Jira Software so your Service agents don’t have to copy and paste details between issues. Configured by the Jira administrator, recipes allow you to decide which details you want to copy. To make maintenance simple, a project picker can be used to select the target Software project.

Trigger on transition, or any Automation trigger

To automate your escalation process as much as possible, you can add Elements Copy & Sync recipes to post-functions so issues are copied as soon as the original support request is transitioned. Or you can trigger the recipe when an SLA is breached by using the REST API in an Automation rule.

Synchronize comments or status from developers back to Jira Service Management

Copy and synchronize comments one way or bi-directionally between issues so developers and agents can collaborate seamlessly. Workflow status synchronization makes life easier for agents by automatically resolving the support request when the Software issue is closed.
Configure automatic escalation of issues from JSM to Jira Software so your Service agents don’t have to copy and paste details between issues. Configured by the Jira administrator, recipes allow you to decide which details you want to copy. To make maintenance simple, a project picker can be used to select the target Software project.
To automate your escalation process as much as possible, you can add Elements Copy & Sync recipes to post-functions so issues are copied as soon as the original support request is transitioned. Or you can trigger the recipe when an SLA is breached by using the REST API in an Automation rule.
Copy and synchronize comments one way or bi-directionally between issues so developers and agents can collaborate seamlessly. Workflow status synchronization makes life easier for agents by automatically resolving the support request when the Software issue is closed.

Tutorial

Synchronize the status of two issues

When a support ticket is escalated to a development project, it often means that the support ticket won’t be closed until the escalated issue has been fixed by the software team. As a support agent, it’s bothersome to have to check the status of an escalated issue. You can automate the process with Elements Copy & Sync.
Copy & Sync Product Manager: Thibaut

Have questions about escalating Jira issues from one project to another?

FAQ

Can I copy Forms?

Yes, Forms, previously known as ProForma, can be copied by Elements Copy & Sync and added to the Jira Software issue so developers have the information they need.

Can I copy all the comments in the original support request?

Yes, you can copy all the comments made at the time of escalation, and you can also choose if you want any new comments, or modifications of existing comments to by synchronized over to the escalated issue.

Can I control who can trigger cloning the issue?

If you chose to manually trigger the issue, you can set conditions on the role or group of the user to control who can escalate issues.
More use cases

One app, 100+ use-cases

Discover more ways your team can use Elements Copy & Sync to standardize your processes.

Leverage a template project in Jira by bulk copying issues

Streamline your process control by bulk copying Jira issue templates

Create multiple subtasks for software testing

Automatically create multiple testing issues in Jira thanks to a set of templated subtasks

Create multiple issues dynamically for employee onboarding

Simplify the work of HR teams using Jira by creating all tasks linked to a new employee onboarding