JIRA - Focused Build Requirements SP04 (Standard)
- CrossALM
- Daniel Triftshaeuser
- 1 SAP Configuration
- 2 Jira Configuration
- 2.1 Connection Template
- 2.1.1 Configuration Profile
- 2.2 Outbound Configuration
- 2.2.1 Status Mapping
- 2.2.2 User Mapping
- 2.2.3 Text Mapping
- 2.2.4 Field Mapping
- 2.1 Connection Template
Basic synchronization for Focused Build Requirements. Includes creation from Jira as well as limited status sync from SolMan to Jira. This template uses the Focused Build Standard API and supports all FB SPs versions beginning from version 4.
SAP Configuration
This page details the set up process on Jira side, for the SAP side counterpart please refer to the following page SAP - Focused Build Business Requirement (Standard)archived.
Limited status change functionality is also supported from SAP → Jira as described here SAP - Focused Build Requirements (Standard & PLUS) - Status Synchronization from SAP Solution Manager to Jiraarchived
Jira Configuration
Connection Template
Configuration Profile
Please maintain the value of the External System GUID given during configuration on SAP side:
SAP - Focused Build Business Requirement (Standard)archived
Outbound Configuration
For this template we are working with the standard service provided by Focused Build for Support packs 04 to 07. Meaning we are limited to mapping the data as specified below.
Please follow the detailed instructions given on the following page collection
3. Outbound Configurationarchived
Status Mapping
Outbound status update is not supported by this template.
User Mapping
User function Name | JSON Key | Description | Mandatory? |
|---|---|---|---|
Owner | IvOwnerUser | The owner for the requirement | yes |
Business Process Expert | IvBpexUser | The Business Process Expert for the requirement | yes |
Text Mapping
Text Name |
| Description | Mandatory? |
|---|---|---|---|
Description (long) | IvDescription | Multi line text field that contains the description of the requirement | yes |
Solution Description | IvSolution | Multi-line text field that describes the solution for the requirement |
|
Assumptions | IvAssumption | Multi-line text field that describes the assumption for the requirement |
|
Field Mapping
Field Name | JSON Key | Description | Mandatory? |
|---|---|---|---|
Summary / Title | IvTitle | Single line field that represents the title of the requirement | yes |
Local Flag | IvLocal | Check box that describes if the Requirement is Local |
|
Value Points | IvValuePt | Number that represents the value points for the requirement |
|
Effort Points | IvEffortPt | Number that represents the effort points for the requirement |
|