...

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

...

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

Controls if the inbound 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.

...

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

Worker Threads setting

This setting controls how many worker threads iHub will use to process the queue of requests. Default is 2. Consider increase this number if there is a lot of calls and long running calls.

Each node in a Jira datacenter setup will have the numbers specified, so if you run 4 nodes, the default is 2 x 4 = 8 worker threads in totoal.

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