The platform-specific setting of the Exalate app. Depending on a platform, Exalate app has some general settings in the admin menu.
Jira Server
Proxy User - Exalate performs issue changes on behalf of this user. You can use an existing JIRA user or create a new one. More details.
Email Notifications - notification messages, sent to email. Use the toggle to enable/disable email notifications.
In-Jira Notifications - flag messages containing confirmation, alerts, and acknowledgment related to the Exalate application. Use the toggle to enable/disable flag notification messages.
Authentication required - Relevant only for connections with Exalate 3.x and lower. Use the toggle to enable/disable authentication to your instance and secure the connection. Note that if you set the authentication as required, you will need to share the credentials with the remote instance so they could authenticate to your instance.
Polling Interval(in seconds) - a certain time interval used to poll the Destination instance in case your instance is not publicly accessible.
Show Exalate and Connect actions - you can configure whether to display the Exalate and Connect buttons on the issue view. Use the toggle to enable/disable the button state.
Show Unexalate actions - allows displaying the Unexalate button on the issue view. Use the toggle to enable/disable the button state.
Hide inactive connections - allows to hide connections that are no longer active from manual exalate options.
Display URL - the URL, which is used to access your JIRA instance from the public network.
Jira Cloud
JIRA Cloud URL - your JIRA Cloud instance URL.
Exalate URL - the Exalate application URL.
Show Exalate and Connect action - you can configure whether to display the Exalate and Connect buttons on the issue view. Use the toggle to enable/disable the button state.
Show Unexalate action - allows displaying the Unexalate button on the issue view. Use the toggle to enable/disable the button state.
Hide inactive connections - allows to hide connections that are no longer active from manual exalate options
HP ALM/QC
You need to Configure the Exalate app to communicate with HP ALM/QC instance under General Settings.
HP ALM URL - the URL of the HP ALM/QC instance without /qcbin path
Exalate URL - the URL of the server, where an Exalate application is installed
HP ALM user - the user that acts as a proxy user. Exalate will communicate with HP ALM/QC on behalf of that user.
Password - the password for the HP ALM user.
Do they need to know our HP ALM user/password? - Use the toggle to enable/disable authentication to your instance and secure the connection. Note that if you set the authentication as required, you will need to share the credentials with the remote instance so they could authenticate to your instance.
GitHub
Exalate URL - the Exalate application URL
Account - the GitHub account used to install the Exalate application
Zendesk
Exalate URL - the Exalate application URL
Proxy User - Exalate performs issue changes on behalf of this user. This user must be a dedicated zendesk agent. More details.
Token - Access Token generated by the proxy user.
Servicenow
Issue Tracker URL - your Servicenow instance URL.
Proxy User - Exalate performs issue changes on behalf of this user. This user must be a dedicated servicenow user. More details.
Proxy password - The Proxy user password.
