In this scenario, you synchronize a customer's Jira project with your 1st level support team's Jira Service Desk project.
This scenario is recommended for important customers who you work closely with (hence the name 'Power Customer') as it lets them sync their Jira issues straight to your Jira Service Desk, rather than manually create new requests corresponding to their Jira issues.
- All comments made by the 'Power Customer' will be created as public comments in the 1st level Jira Service Desk system.
- Public comments made in the 1st level support's Jira Service Desk system will appear as standard comments in the Power Customer's Jira system.
- Issues created by the customer will be mapped to the 1st level support's Jira Service Desk project, but issues will usually not be created in the other direction.
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 synchronize projects on separate Jira systems, but the configuration here is very similar.
Set up projects
Establish the connection
Now, we have to establish a connection between Project A and Project B.
- In Project A, click Project settings > Issue Synchronization > New synchronization, and select Synchronize within this Jira instance (you can also synchronize with another instance, but for the moment we'll sync within this instance for the sake of simplicity).
- On the New synchronization screen, choose the project you want to sync to (in this case, Project B):
- Assign the synchronization a suitable name, and click Send Request.
- To accept the request, open Project B and click Project settings > Backbone Cloud-to-Cloud > in the Actions column, click ... > View Request > Accept Request > Start configuration
Now we've connected the projects, it's time to configure some synchronization settings.
Configure the synchronization
Now, we'll tell Backbone what data to synchronize, and which JIRA Service Desk scenario we want to use.
- 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 Power Customer scenario, click Start configuration for the Power customer support requester option:
- On the Issue Type Mappings tab, click New Issue Type Mapping to map issue types. Select First to Second, and click Next.
- On the Create Issue Type Mapping screen, you can map Jira issue types in Project A to Jira Service Desk issue types in Project B. Map the Task, New Feature, and Improvement Jira issue types to the IT Help Jira Service Desk issue type.
- The next step is to configure the synchronization of Jira Service Desk customer request types. Start by going to the Fields – Default Values tab.
- On the Project B column, click the + button to open up the Create Default value screen. In the Field box, select Customer Request Type, uncheck the All Issue Types box, and map the following Issue Types:
- IT Help to the Default value Get IT Help
- Purchase to Default value Purchase request
- Access to Default value Request a new account.
- On the Field Mappings tab, click on Suggestions to map fields. Select the Summary and Description fields.
- On the Comments tab, you must enable comments and select the Enriched mapping option (so that when comments are synced between the Power Customer and your 1st level team, you know exactly who wrote them).
To start the synchronization, click Publish Draft > Start.
Comments made by the Power Customer in Project A will appear as public comments in Project B. Public comments made by 1st level support in Project B will appear as standard Jira comments in Project A.
Basic configuration is now complete – you can now go further and configure additional Field Mappings.