...
Action Type | Comment | Recommended Description | |
|---|---|---|---|
Initial | Used right after creation via the plugin | Created, New | |
Delete | Used after the transport request is deleted either in the managed system or via the plugin. The transport remains in the list with this status description set. | Deleted | |
Release | Used when the transport has been released in the managed system and therefore, cannot be deleted anymore. | Released | |
Couple | Used when wanting to add transport requests that already exist in the managed system | Couple, Added, New | |
Decouple | Used for removing the link of the transport to the specified Jira issue and makes it disappear from the list | Decouple a description is not relevant, as the it will vanish from the list | |
Import | Uses to import transport request in th next system. | Import | |
Custom | You are also free to define your own actions. You can define as many custom actions as you see fit. Action type Custom is not used for technical operations on the transport itself and acts as a custom label as well as triggering the mail notification below. | up to you | |
Sort | Used to sort the list of the transport requests | Sort | |
ToC | Used to create and import a transport of copies in the next system. The ToC will be shown in the list. | Transport of copies | |
Upload | Used to upload a transport request. | Upload |
After creating the Customer Actions you will be able to see them:
...