Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Current »

Jira End-Users will need specific authorizations to be able to interact with Transport Requests when they are using the Cross Connector. To customize the authorization groups, in the section “Customer Actions”, define which group can have access to which functionality:

End-Users assigned to the group cross-connector-transport-admin can interact with all of the Cross Connector features.

The following table describes how the authorization groups function:

Action Type

Explanation

INITIAL

End-Users assigned to the group described on the field “User Group” will be able to create “Transport Requests”.

Button “New” is visible.

DELETE

End-Users assigned to the group described on the field “User Group” will be able to delete “Transport Requests”.

Button “Delete” is visible.

RELEASE

End-Users assigned to the group described on the field “User Group” will be able to release “Transport Requests”.

Button “Release” is visible.

COUPLE

End-Users assigned to the group described on the field “User Group” will be able to couple “Transport Requests”.

Button “Couple” is visible.

DECOUPLE

End-Users assigned to the group described on the field “User Group” will be able to decouple “Transport Requests”.

Button “Decouple” is visible.

IMPORT

End-Users assigned to the group described on the field “User Group” will be able to import “Transport Requests”.

Button “Import” is visible.

image-20240408-092707.png

TOC

End-Users assigned to the group described on the field “User Group” will be able to create “Transport of Copies”.

Button “Create ToC” is visible.

image-20240408-093917.png

SORT

End-Users assigned to the group described on the field “User Group” will be able to sort“Transport Requests”.

Button “Sort” is visible.

image-20240408-110613.png

CUSTOM

End-Users assigned to the group described on the field “User Group” will be able to execute the custom action.

Actions can use the same User Group to increase the flexibility during the development of the Authorization Concept. An example of how the groups can be used if found below:

How to create User Groups

Select User Management in your Jira instance, click on Groups and create a new group on the section Add group.

Find the group you have created and click on Edit members.

Then add the members to the group.

After this last step you will be able to start using the Cross Connector for TMS according to the authorization concept you have developed.

  • No labels