The template Focused Build Requirements SP08 will use the enhanced interface recently introduced that allows synching syncing of relevant fields into Focused Build Requirements as well as status and field synchronization from Jira to SolMan.

It allows syncing of data directly via technical keys without having to use intermediary despritors.

From Solution Manager only the status can be synchronized back to Jira.

SAP Configuration

For more details, please check the page SAP - Focused Build Requirements (PLUS).

Jira Configuration

Choose the correct Template for your Connection Profile:

...

There are no more mapping tables necessary in Solution Manager with this version of the template. The only thing that needs to be insured is an established connection between Jira Server and Solution Manager. Refer to this page so see how to set it up

Jira Configuration

Connection Template

...

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

Check out this page for a good overview 1.1 Connection Profile .

Please Note:

In SP08 the field “Configuration Profile” does not require a mapping to be set up in Solution Manager and only serves as an identifier.

Please make sure that all options under 1. Global Configuration are well maintained.

Mapping

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

Status Mapping

...

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 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
4. Master Data → 4.1 User Mapping

Text Mapping

...

All single and multi line text fields can be used for synchronization as well as they 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 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.