In the Synchronization Objects configuration, you will define which Issue Type will be connected to which Transaction Type in SAP Solution Manager.
To start using the configuration you need to choose the connection profile.
Transaction Type
The transaction type you can map here depends on your selection of connection template.
Please refer to this page for more information Connection Templates
Name of Template | Available Process Types |
|---|---|
Focused Build Requirements SP04 (Standard) | S1BR |
Focused Build Requirements SP04 (PLUS) | S1BR |
Focused Build SP04 - Work Packages and Work Items | S1IT, S1MJ, S1GC |
Focused Build Requirements SP08 | S1BR |
Solution Manager V1 | freely definable |
Document Name
This information will be visible on the Issue Type when the synchronization is executed.
Enabling condition
This field is used for create an additional trigger condition based on a Jira Custom Field. The rule below will be followed depending on the selected value of this field:
No
If the field is set to no, ALL tickets of the specified Issue Type (Story, Task, etc) will be considered and synchronized trigger for SolMan.
Yes
If the field is set to YES, the fields “Custom Field ID” and “Custom Field Value” must be fulfilled and the synchronization will only be triggered when the Jira Issue type matches to this condition.
Custom Field ID
The custom field id which is used as trigger. This custom field id must be of the type "Select List (single choice)".
Custom Field Value
The value that the field must have to trigger the synchronization.
Ex: only when the custom field has the value “Yes” the trigger can be executed.
Attention: The outbound synchronization is triggered based on the combination of the configurations of Synchronization Objects and Outbound Status Mapping.
In other words, the outbound synchronization will be only triggered to the status registered in the Outbound Status Mapping.
Recommendation:
When Enabling condition is used, it is recommended to follow the guidelines below:
Set the used Custom Field to be mandatory.
This field should be available only on the “Create screen”.
Do not allow users to change this field on the “Edit screen”.