This template allows synchronization of Work Packages and Work Items from Jira to Solution Manager according to the standard Focused Build Integration Process. Creation from Jira into Solution Manager including status changes as well as limited status changes from Solution Manager into Jira are supported. This template uses the Focused Build Standard API and supports all SolMan and FB SPs versions.

Process Overview

The synchronization between this template and the Focused Build Work Packages and Work Items will happen according to the standard Focused Build Integration process. In order to enable the Focused Build process, the process will be mapped according to the following entities:

Work Packages

The Work Packages will be synchronized from SolMan to Jira. There is no interaction from Jira to SolMan in this case:

Open

Work Items

Work Items are created automatically via Work Packages. The synchronization to Jira is just executed when the ticket is created. After that, all status changes for the Work Items should happen in Jira:

Open

Focused Build Process Workflow

Please, check the Standard Focused Build overflow. Please, pay special attention to the moments where the status are automatically change in the Focused Build Process.

SAP Configuration

This page details the set up process on Jira side, for the SAP side counterpart please refer to the following page https://crossalm2.atlassian.net/wiki/spaces/JSMI/pages/6555533427 .

Jira Configuration

1. Global Configuration

1.1 Connection Profile

Create a new Connection Profile for your Project:

• To enable the connection with Focused Build, chose the template FB_SP04

• The unique Config. Profile must be the sam PPM Project ID for the SAP Project you want to synchronize:

  • SM_WORKCENTER → Focused Build - Project Manager → New Project

1.2 Synchronization Objects

Create the sync. objects needed for Focused Build:

1.3 Priority Mapping

Create the priority mapping according to what is available in SolMan:

2. Inbound Configuration

2.1 Status Mapping

The status should be mapped according to when SolMan triggers the Jira Interface.

Work Items (S1MJ and S1CG) does not synchronize status change to Jira.

2.2 User Mapping

Map the users according to the configuration in SolMan. The configuration can be checked in the customizing External Integration Profile.

Work Package (S1IT)

In Jira, both partners should be configured as shown below:

Work Item (S1CG)

Attention: If you don’t wish to add the Requester as partner, you need to plan a strategy of how to use BP Teams during the synchronization process.

Work Item (S1MJ)

Attention: If you don’t wish to add the Requester as partner, you need to plan a strategy of how to use BP Teams during the synchronization process.

2.3 Text Mapping

Work Package (S1IT)

Work Item (S1CG)

Work Item (S1MJ)

2.4 Field Mapping

If you need to work with dates from SAP side, please use the function “Convert from SAP Date”.

If you want to use the field “Original Estimate“, you must respect the format expected from Jira:

• Example 1: 52d

• Example 2: 36h

• Example 3:  3w 4d 12h

If you want to bring the Multi-Categorization from SolMan, please use always the field “Labels” for this purpose. Each word sent from SolMan will be added as a differente label. Categories with more than 1 word will have the spaces preplaced by underscore (ex.: Incidents Management will be in Jira Incidents_Management).

Work Package (S1IT)

S1IT was mapped into a Epic:

• DESCRIPTION is used in the Jira Field Summary

• DESCRIPTION is also used in the Custom Field that represent the Epic Name

• CATEGORY is used as Labels

• CREATED_AT is not mandatory field and it was used to test the conversion of dates to Jira Environment

Work Item (S1CG)

S1CG was mapped into a Task:

• DESCRIPTION is used in the Jira Field Summary

• CATEGORY is used as Labels

• PARENT_EXTERNAL_ID is used to the Jira Field Epic Link to connected dependent tickets

Work Item (S1MJ)

S1MJ was mapped into a Task:

• DESCRIPTION is used in the Jira Field Summary

• CATEGORY is used as Labels

• PARENT_EXTERNAL_ID is used to the Jira Field Epic Link to connected dependent tickets

3. Outbound Configuration

3.1 Status Mapping

Work Package (S1IT)

No Outbound configuration should be done for Work Packages.

Work Item (S1CG)

Outbound configuration for Work Items are only used for Status Change.

Work Item (S1MJ)

Outbound configuration for Work Items are only used for Status Change.

4. Master Data

Do not forget to map the BP of the users that you will use for the interface.

[Link 4. Master Data]