Visible for Role & Group hides/shows the issue tab Integrations

Respond with POST data and triggered action(s) to the client

Controls if the incoming end point shall return what rule was triggered or just 200 OK

Show if an invalid JQL condition is provided in the execution log

Default Off - for events this will log if an JQL is not valid, since all event handlers will pick up this it will show on all actions that listen to that event.

Example

Action A with JQL: project = A with On Create event

Action B with JQL: project = B with On Create event

then if an event occurs it will log on both actions if the JQL was met or not.

Log retention setting

By default the log retention is Off, specifying 0 (zero) as the number will turn the log retention off.

Log retention runs each night at 05:00 and performs a search for all log entries older than the days specified in the setting. So if there is a setting for 30, the log retention will look for logs older than 30 days and delete those from the database.

Why is this useful? In large scale or highly used integration there might be a big amount of response data stored in the database, this can lead to long backup times and out of disk space on the database.

What should I do if I want to keep the logs longer without using the database? Use the log appender properties to save the execution log and incoming log to files, backup these files to a storage area or read them into a log management too. Read more how to set this up here iHub Logging on tomcat server

Proxy Settings

Disabled by default. If the Jira server is behind firewalls and do not have internet access except by using a proxy, then use these settings to tell iHub what proxy to use.

Proxy Port	Port on which the proxy listen to
Proxy Host	The address to the proxy server, could be IP or hostname
Non-Proxy Hosts	Define a pattern when to not use a proxy, e.g. localhost \| *rixter.se

Pagination settings

This setting controls how many iterations iHub maxium can do, this is to prevent infinity loops if the action is configured wrongly or API returns an endless loop of arrays.

Default is 150, meaning it will make 150 request and if more is in the queue it will stop and give an error in the Execution log.

Mutual TLS Settings

Setting will tell iHub what keystore and password to use for Mutual TLS. See more on how to TLS and Certificates for guides.
Mutual TLS will try to load the default keystore if no settings is applied. It will also try to use the paths from the java params below.

-Djavax.net.ssl.trustStore=/home/jira/cacerts 

-Djavax.net.ssl.trustStorePassword=changeit 

-Djavax.net.ssl.keyStore=/home/jira/cert-new 

-Djavax.net.ssl.keyStorePassword=changeit

We recommend to use the settings and use a specific keystore for mutal tls.