JIRA - Focused Build Requirements SP08
- CrossALM
- 1 SAP Configuration
- 2 Jira Configuration
- 2.1 Connection Template
- 2.1.1 Configuration Profile
- 2.1.2 Other
- 2.2 Content Mapping
- 2.2.1 Status Mapping
- 2.2.2 User Mapping
- 2.2.3 Text Mapping
- 2.2.4 Field Mapping
- 2.1 Connection Template
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 SAP - Focused Build Business Requirement SP08archived
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 additional information 1.1 Connection Profilearchived .
Configuration Profile
Name of External Configuration Profile given during SAP sided setup found here
SAP - Focused Build Business Requirement SP08archived
Other
Please make sure that all remaining options under 1. Global Configurationarchived are well maintained.
Content 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 Mappingarchived
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
Partner Function | Technical Name - JSON key |
|---|---|
Business Process Expert | /SALM/01 |
Requirements Team | /SALM/13 |
Owner | HT000012 |
Please keep in mind that the partners you are syncing need to be mapped in section
4. Master Data → 4.1 User Mappingarchived
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
Text Type | Technical Name - JSON key |
|---|---|
Description | S115 |
Assumptions/Comments | S126 |
Solution Description | S004 |
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 Mappingarchived
Field Name Solution Manager | JSON Key | Mandatory? |
|---|---|---|
Description (Summary) | title | yes |
Priority | priority | yes |
Values Points | valuePt |
|
Effort Points | effortPT |
|
Local Flag | local |
|
Requirement Classification ID | classification |
|
Planned Project ID | plannedProject |
|
Please note:
The fields “Category” and “WRICEF ID” can currently not be mapped. This feature is shipped in a later version.