Configure SAP for the connection with Jira

Some topics are SAP specific and are therefore configured in SAP. Here is an overview of the possibilities. To ensure a smooth process, we recommend configuring the following topics on all systems.

Content

Preparation for the Jira communication

In addition to importing the transports, minor adjustments must be made after installation.


ProcedureExample
1Typically, the SAP instances are protected by a firewall. In order for communication to be possible, make sure that Jira can access the SAP system via HTTP. In general the best way to do this is to contact your internal IT department.
2

Create a Communication user with role /IX2/JTMS_SERVICE for Jira in SAP with minimal permissions for the communication with Jira. This user will be used to modify transports and is stored in per SAP system.


3

You need to make adjustments to the role /IX2/JTMS_SERVICE for future updates via the transaction PFCG

Change the physical filename in the permissions for file access (technical name: S_DATASET) to match you SAP Systems transport directory. 

You can find the transport directory in the directory assigned to the parameter DIR_TRANS in transaction AL11.

Make sure to add /* for Unix/Linux or \* for windowssystems to the path.


4

Create a Attribute to store the linked Jira issues via the transaction SE03. In the Administration area, select Display/Change Request Attributes and create the new attribute with e.g. the name ZJIRA

5

Create a RFC destination with the name JIRA Update Issue and type G that points to Jira via the transaction SM59. Therefore define the Host and Path Prefix. There is no Logon Procedure necessary in this form, because it is done via an API Token in the sepearte SAP Transport Panel Setting in SAP. See the section SAP Transport Panel Customizing on this page for further information.  

The Request URLs are randomly generated for each App installation. Therefore the Request URL can be found in the app configuration of your Jira system Settings Apps SAP Transport Panel API settings Request URL. Afterwards you need to split the Request URL into Host and Path Prefix for the setting of the RFC destination in SAP. 

See in Jira Settings Apps SAP Transport Panel API settings Request URL Update Issue

Request URL in Jira 
https://898ea802-512b-4d8f-a551-4dfa2a73b4a4.hello.atlassian-dev.net/x1/sYEWHtwPMw14apwtgzLk2twNVcw
Host in SAP Path Prefix in SAP
https://898ea802-512b-4d8f-a551-4dfa2a73b4a4.hello.atlassian-dev.net/x1/sYEWHtwPMw14apwtgzLk2twNVcw


Also go to the Special Options Tab and set the Compression Status to Inactive, so SAP will not compress the data.


6

Create a RFC destination with the name JIRA Update Transport Status and type G that points to Jira via the transaction SM59. Therefore define the Host and Path Prefix. There is no Logon Procedure necessary in this form, because it is done via an API Token in the sepearte SAP Transport Panel Setting in SAP. See the section Configure Import Feedback on this page for further information.  

The Request URLs are randomly generated for each App installation. Therefore the Request URL can be found in the app configuration of your Jira system Settings Apps SAP Transport Panel API settings Request URL. Afterwards you need to split the Request URL into Host and Path Prefix for the setting of the RFC destination in SAP. 

See in Jira Settings Apps SAP Transport Panel API settings Request URL Update Transport Status

Request URL in Jira 
https://898ea802-512b-4d8f-a551-4dfa2a73b4a4.hello.atlassian-dev.net/x1/sYEWHtwPMw14apwtgzLk2twNVcw
Host in SAP Path Prefix in SAP
https://898ea802-512b-4d8f-a551-4dfa2a73b4a4.hello.atlassian-dev.net/x1/sYEWHtwPMw14apwtgzLk2twNVcw

Also go to the Special Options Tab and set the Compression Status to Inactive, so SAP will not compress the data.

7

SAP Transport Panel is shipped with a default configuration that can be adjusted as you wish via the transaction SM30. See the section SAP Transport Panel Customizing on this page for further information.  


8If you want to see the Return code of SAP transports imported on your productive System in Jira, you need to activate the BAdI CTS_IMPORT_FEEDBACK in your productive SAP System. See the section Activate Import Feedback on this page for further information.


9

Add a Schedule Job to ensure updates to Jira via the transaction SM36, when changes are done in SAP. See the section Schedule Update Job on this page for further information.  


SAP Transport Panel Customizing

SAP Transport Panel is shipped with a default configuration that can be changed by editing the table contents of the SAP Transport Panel Customizing View /IX2/JTMS_CUST in the transaction SM30. If you develop on multiple systems this customizing needs to be adjusted on each system. 

FieldDescriptionExample
ActiveEnable or disable the whole functionality.



Update TitelThe Titel of the issues and Transports will be updated. Enable or disable the functionality via this checkbox. 
ToCs 

Select whether all objects or objects in active transport tasks should be released when the creation of a transport of copies is triggered by Jira.

Jira web URLAtlassian Jira is started when a issue is selected in the SAP transport by double-clicking on it. Here you enter the path to Atlassian Jira, where the issues can be found.
Attribute

For the Jira issue link SAP Transport Panel uses the transport attributes. Enter the name for the created attribute in this field. 

RFC DestinationStore the created RFC destination for Update Issue for communication with Jira.
Auth Token J. CloudFor authenticated connection with SAP Transport Panel for Jira Cloud, you have to generate a token in SAP Transport Panel.
Naming transports

Select a naming convention for a transport created via Jira. 

Naming ToC

Select a naming convention for a transport of copies created via Jira. 


Schedule Update job

If you want your SAP system to update the Jira issues according to changes that where made in SAP and not in Jira you need to schedule a SM36 job in your development systems with the following parameters. If you develop on multiple systems this job needs to be added on each system. 

ParameterSetting
Job NameJTMS_UPDATE_JIRA_TRANSPORT_STAT
UserEnter a user with the permissions of the role /IX2/JTMS_SERVICE.
ABAP Program/IX2/JTMS_UPDATE_JIRA_TR_STATU
VariantLeave this empty. The default settings will update all transports modified in the last year. 
Period Set to "Each hour" or shorter interval.


Configure Import Feedback

If you want to see the Return code of SAP transports imported on your productive System in Jira, you need to activate the BAdI CTS_IMPORT_FEEDBACK in your productive SAP System and set a RFC destination.

Activate Import Feedback

Activate the BAdI CTS_IMPORT_FEEDBACK in your productive SAP System.


Procedure
1Call the transaction SE18
2

Enter BAdI Name CTS_IMPORT_FEEDBACK

3Select Display
4Navigate to Implementation → Change
5Select /IX2/JTMS_BADI_IMPRT and press Continue
6Click on Activate Business Add In Implementation

Set RFC destination

Store the created RFC destination for Update Transport Status for communication with Jira.


ProcedureExample
1Call the transaction SM30


2Enter Table /IX2/JTMS_STMS_C and press Maintain


3Store the created RFC destination and the Auth Token from Jira Cloud for communication with Jira. For authenticated connection with SAP Transport Panel for Jira Cloud, you have to generate a token in SAP Transport Panel.


4Save your settings