Release a transport in SAP via Jira transition
When all approvals are done and the quality of the transport is assured the transport can be released on a productive system in SAP. Therefore the related issue is solved and all related transports in SAP can be released and are not editable anymore. Afterwards the transport can be imported on a productive system.
Transition:SOLVED → READY FOR PRODUCTION
SAP Transport Panel: Original Transport Management workflow
- The original SAP transport, which is linked to the Jira issue, and all related tasks are released in SAP.
Content
Step-by-step guide
Release a transport via issue
| Step | Procedure | Example |
|---|---|---|
| 1 | Navigate to the correct project and click on the left navigation bar on Issues. Open an issue of the type Customizing request in the status Solved (or move an issue in this status). For further information on how to find and open an issue, please use the Atlassian documentation: Search for issues in a project | |
| 2 | Click on the Workflow Drop-Down via click on Ready for production |
|
| 3 | The issue is now in the status Ready for production. Directly after the transition the linked transports and all tasks are released in the SAP System and they are not editable anymore in Jira. Normally a SAP admin will take this transport and import it on a productive System. After the import step the corresponding Return code is set in Jira. After a scheduled period the field Return code is checked in Jira and the issue is automatically moved from the status READY FOR PRODUCTION to the status IN PRODUCTION depending on the field content (How to configure an automatic transition based on the Return code of SAP Transport Panel). |
|
Release a transport via Kanban board
| Step | Procedure | Example |
|---|---|---|
| 1 | Navigate to the correct project, click on the left navigation bar on Kanban board. | |
| 2 | Search for an issue of the type Customizing request in the status Solved (or drag an issue in this status). Drag the issue to the column Ready for production. |
|
| 3 | The issue is now in the status Ready for production. Directly after the transition the linked transports and all tasks are released in the SAP System and they are not editable anymore in Jira. Normally a SAP admin will take this transport and import it on a productive System. After the import step the corresponding Return code is set in Jira. After a scheduled period the field Return code is checked in Jira and the issue is automatically moved from the status READY FOR PRODUCTION to the status IN PRODUCTION depending on the field content (How to configure an automatic transition based on the Return code of SAP Transport Panel). |
|
Optional Test
- Check SAP System, if the transport is released.
Nothing happend?
Check the comment section of the Jira issue to get messages from Jira as well as messages from SAP.