Cloud - Visibility Settings

Owned by CrossALM
Last updated: May 29, 2024 by Kristin Hildebrand
3 min read

The Visibility Settings is the section of the configuration that defines when the Cross Connector should be visible on your Jira issues.

For this, navigate to TMS Component Activation and select Add Visibility Settings.

image-20240528-142234.png

 Fill out the following information (screenshot filled with mock data)

image-20240528-142340.png

 

Jira Project

The project in which the Cross Connector should be visible.

Jira Issue Type

The Jira Issue Type for which the Cross Connector should be visible.

Customfield ID

The ID of your custom field that is being used to control visibility.

How to create a custom field and identify its ID can be found here:

CustomField Values

The values of the custom field that will be used to control visibility of the Cross Connector UI block.

The values you have to write here is dependent on the type of custom field you use.

If you are unsure how the values of your custom field are stored you can use the following API call:

<JIRA_SERVER_URL>/plugins/servlet/crossalm/cc5/cc_transport_management?type=get-customfield-value&jiraIssueKey=<JIRA_ISSUE_KEY>&customfieldId=<CUSTOMFIELD_ID>

The output could look this:

{"customfieldId":"customfield_10113","value":"FSP"}

Jira Final Status

In this field place the status from the Issue Type chosen in the field Jira Issue Type with which the component will be rendered as read-only.

SAP Settings

Enables you to register multiple development systems to be used in your application. The development systems defined in this section will be available for the end user in the Dropdown List “Dev. System”.

SAP System Type

The SAP System Type for which transport requests will be created.

Currently, only ABAP systems are supported.

SAP Client

The SAP Client in which the transport requests will be created.

SAP CTS Project

You can place in this field the CTS project available in the SAP system.

Please, note that the CTS Project Switches can affect the way the Transport Requests works.

Default Import Settings

With this Settings you can disable import Settings or check them by default.

Visibility of Activities

The checked activities will be visible. All unchecked activies will be hide.

Transport Description Settings

Here you can add a Template how the Transport Request Description should look like.
Issue fields can be added with {{issue.fields.fieldname}}.
{{description}} add the “short description” from create action.

 

After having finished creating a Visibility Setting you should see it on the list.

 

 

Note that you can have multiple Visibility Settings for different systems by pressing the button Add Visibility Settings again.

Verify

Create a new issue, where the value for the custom field you have specified has not yet been determined.

Add the app to the issue layout by selecting it from the installed app list.

When first rendered the issue view component will inform you that it is not active for the selected issue.

 

Now place the value specified in the configuration.

I am using field “Landscape” and value “ERP” as indicated by the screenshots above.

Now the UI block is available and allows for transport request creation for the specified system, provided you have the necessary authorization.