In this scenario, you synchronize your 1st level support's Jira Service Desk system with your 2nd level support's Jira installation:

This allows 2nd level support to help 1st level agents by making comments which are synchronized from their Jira system to the 1st level team's Jira Service Desk.

In this scenario, issues are usually created in the Jira Service Desk – they can be created on the Jira side, but this is unusual and requires different permissions.

Configuration Guide

Now, we will configure this scenario as a guide. The two sample projects will be configured on the same Jira system: in most real world scenarios, Backbone will integrate projects on separate Jira systems, but the configuration is very similar in both cases.

Configure the synchronization user

  • Add the synchronization user to the jira-service-desk-users group
  • Assign the Service Desk Team role for all synchronized Jira Service Desk projects.

Set up projects

Firstly, set up the two projects that will be synchronized: Project A as a Jira Service Desk project and Project B as a Jira project.

Establish the connection

Now, we have to establish a connection between Project A and Project B – please refer to the guide to creating a new synchronization for step-by-step instructions.

Configure the synchronization

Now, we'll tell Backbone what data to synchronize, and which Jira Service Desk scenario we want to use.

  1. On the Issue Synchronization screen, the actions column, click ... > Configure to open up the configuration UI. This brings up the Jira Service Desk scenario selection page. As we are configuring the 2nd level support scenario, click Start configuration for the Second level support requester option:
  2. On the Issue Types tab, click New Issue Type Mapping to map issue types.
  3. In the dialog select First to Second, and click Next. On this screen, you can map one or multiple Service Desk request types to a single Jira issue type. In this example, we have mapped the PurchaseIT HelpAccess, and Fault Service Desk request types to the Task Jira issue type.
  4. On the Fields - Mappings tab, click Suggestions, and tick the Description and Summary field to synchronize them.
  5. On the Comments tab, enable Comment Synchronization, and select the Enriched mapping option (so that when comments are synced between your 1st and 2nd level teams, you know who wrote them).

To start the synchronization, click Publish Draft > Start.

Now, comments made by your 2nd level support team will appear as internal comments in the 1st level team's Jira Support Desk system.

Next steps

Basic configuration is now complete – you can now go further and configure additional Field Mappings.