| Table of Contents |
|---|
| Excerpt |
|---|
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. |
SAP Configuration
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.
...
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 SP08
Jira Configuration
Connection Template
...
Check out this page for additional information 1.1 Connection Profile .
Configuration Profile
Arbitrary descriptor
The value you specify here will be used for building the URL.Name of External Configuration Profile given during SAP sided setup found here
SAP - Focused Build Business Requirement SP08
Other
Please make sure that all remaining options under 1. Global Configuration are well maintained.
...
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 Mapping
...
All single and multi line text fields can be used for synchronization as well as they 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.
...
Check out this page for a more detailed explanation 3.4 Field Mapping
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.