This template will use the enhanced interface introduced in SP08 of Focused Build. It allows syncing of Focused Build Requirements directly via technical keys without having to use intermediary descriptors or mapping tables in Solution Manager and therefore makes the configuration more straightforward.

From Solution Manager the status can be synchronized back to Jira with the same limitations as previous versions.

This template uses the Focused Build Standard API and supports all SolMan and FB SPs versions.

SAP Configuration

This page refers to the necessary set up on Jira side, for SAP side configuration please check https://crossalm2.atlassian.net/wiki/spaces/JSMI/pages/6555599042

Jira Configuration

Connection Template

Open

All basic mapping operators have to be mapped here like the external reference URL of Solution Manager.

Check out this page for additional information [LINK 1.1 Connection Profile] .

Configuration Profile

Name of External Configuration Profile given during SAP sided setup found here

https://crossalm2.atlassian.net/wiki/spaces/JSMI/pages/6555599042

Other

Please make sure that all remaining options under [LINK Global Config] are well maintained.

Content Mapping

Map all fields that should be synchronized to Solution Manager under section 3 Outbound Configuration

Status Mapping

Open

Every status in Jira can be mapped to a designated external status in Solution Manager.

The external status specified has to be the technical status definition of Solution Manager.

If requirements in SolMan should be created by creating a Jira ticket or changing its status, make sure that external status E0001 is mapped accordingly.

For more information check [LINK 3.1 Status Mapping ]

User Mapping

All partner fields in Jira can be mapped so that they are sent to Solution Manager and synced to their designated partner function.

The JSON Key specified has be to be technical key of the partner function in Solution Manager.

Default values used in Solution Manager

Please keep in mind that the partners you are syncing need to be mapped in section

1. Master Data →

[LINK 4.1 User Mapping]

Text Mapping

All single and multi line text fields can be used for synchronization as well as for the Jira standard field Description.

The specified JSON key has to be the technical key of the text type in Solution Manager.

Default values

Field Mapping

In this section all main fields of the transaction type are mapped.

The specified JSON keys have to be taken from the table below.

Check out this page for a more detailed explanation [LINK 3.4 field mapping]

Please note:

The fields “Category” and “WRICEF ID” can currently not be mapped. This feature is shipped in a later version.