Configuring global Jira Service Management settings

Attribute default label

The text type attribute to be used as default label for every object type. You can change this on the specific object type configuration too.

Note that this affects only for those object types that are created after this setting has changed.

Attribute default description

The description for the default label attribute. You can change this on the specific object type configuration too.

Open Object dialog event

Determines if the object dialog should open when a user selects an object link or when the user hovers with the mouse over an object link.

This will also apply when you view Assets object fields while you view a Jira issue.

Default number of objects fetched in custom fields

This indicates the number of objects that Assets will fetch in custom fields for each request. The default value is set to 25.

Once the user starts to search any objects on the custom field, more objects matching the search criteria are fetched from server asynchronously. Hence, the default limit of 25 is recommended and should be enough.

If you increase this number, it will affect the performance since more objects would then have to be fetched on every request.

Assets Audit Log enabled

If you check this checkbox, it is ensured that all Assets object events are logged to an audit log file.

Include attribute values in audit log

This checkbox is enabled only if the above "Assets Audit Log enabled" is checked.

If checked, this will include all attribute values of an object in the audit log.

Restore Assets index from file

This will ensure that on start up, Assets index will be restored from a file. This will help increase the startup time. 

Assets will perform a consistency check of the file against the database on startup and recreate the index if they mismatch.

If you uncheck this, you may experience a slower start up time. However, it could remove the risk of a potential corrupted index file which may cause data inconsistency.

By default, this is checked. The file is located at {$JIRA_HOME/caches/assets_indexes}

 E.g, path of the file on MacOS will be {/var/atlassian/application-data/jira/caches/assets_indexes} 

Store cache on shutdown

This indicates that the Assets index should be persisted to a file on Assets shutdown (e.g, in cases of a plugin upgrade, Jira restart, Assets disable etc).

It is recommended that if "Restore Assets index from file" is checked, this property should be switched on too.

Restrict Assets Cache

This helps to limit the amount of objects allowed to be stored in Assets. This will subsequently limit the memory footprint by allowing only a limited number of objects to reside in the cache.

The default and recommended way to use Assets is to not restrict objects in cache. The limit will have negative performance impact.

Number of objects allowed in cache

This is enabled only if "Restrict Assets Cache" is checked.

This property indicates the number of Assets objects that will be be stored in the cache.

The recommended way is to not limit objects in cache.

Maximum File upload size

The maximum file upload size in bytes when uploading files, images, attachments into Assets. 

Assets parallelism

This is number of threads that Assets will spawn to perform parallel tasks, e.g, importing data, re-indexing etc.

If this number is set to a lower value, Assets will put less strain on Jira. However, it will come at the cost of a low performance speed.

Process data sources via temp files during imports

Temporarily store data on disk when using the import modules to reduce memory footprint during import.

This is used to indicate if the data stored in Assets should be sorted by a locale other than Jira's default one.

Fetching of objects may be slower if this option is switched on. Hence, by default, this is disabled to avoid performance issues.

This is enabled only if "Use a custom locale for Assets" is checked.

This determines the language Assets should use when sorting data.

Import temp file buffer size

The maximum number of items stored in memory when processing data sources through temp files

Import temp file alternative directory

Alternative directory for storing temp files on disk during an import if enabled. Restart your instance for changes to this config to take effect.

Maximum parallel imports

The number of parallel imports that can run across your cluster. Learn how to configure parallel imports

Jira Service Management portal search text (single)

Placeholder for the Assets field on the Jira Service Desk portals (Single fields)

Jira Service Management portal search text (multiple)

Placeholder for the Assets field on the Jira Service Desk portals (Multiple fields)

This setting is available only if you have a multi-node Data Center set up.

This node will be the dedicated node to execute Assets scheduling tasks, such as Importers, Automation, manual imports etc.

Note that, if a node was selected as the dedicated scheduling node and happens to be unavailable at the time of running a scheduled task, then that task will not run.

Configure frequency of updates for the Process results tab

Turn on to block Assets imports from external sources that haven’t been configured in the Jira allowlist. How to configure the Jira allowlist

Note that only the following modules can be blocked using the Jira allowlist: Object Schema Import, LDAP Import, JSON Import, CSV Import, Bitbucket environments import, Device42 import, JAMF import, ServiceNow import, and Snow Import.