Certain advanced aspects of Structure's behavior might not have dedicated configuration pages, being controlled by application properties or system properties instead. This page lists Structure-related properties and describes how to set them.
The easiest way to add and manage custom Structure properties and dark features is to use the Structure dark features and Fine Tuning interface.
To access the interface, you must have Jira Administration permissions and enter the interface location directly into your browser:
When an invalid property value is entered in the table, the default value is applied.
Spaces are not trimmed, and may result in an invalid value.
When you delete a property from the admin table, it's property value is set to the default value:
You can set System properties during Startup or using Script Runner.
You can set System properties using the
-D JIRA startup option, for example:
Configuring JIRA startup options is described in this article. You will need to restart JIRA for the properties to take effect.
You can also set system properties using the Script Runner add-on.
The changes take effect after you restart the Structure, but the properties will be reset to their default values when you restart JIRA. In some cases for settings to take effect you have to reinstall the Structure. But If you want the changes to be permanent, please use the
-D startup option as described above.
|The maximum number of rows that one structure can contain. Size exceeding operations will be blocked.|
|The maximum amount of time that can be spent for Structure generation (in seconds).|
When adding generators:
|Setting this property to |
|The maximum number of manual adjustments per one structure. When this limit is reached adding new manual adjustments will be impossible. If you reduce this limit, you may have to remove all manual adjustments for the structures that exceed it.|
The maximum number of manual adjustments per one user action. If this limit is exceeded the action will be aborted without making any changes.
|Set to true to enable support for hidden issue links.|
|Set to true to disable periodical checks of Lucene index consistency.|
Synchronization lets you keep Structure issue hierarchy in sync with some other issue properties.
|Set to true to enable Synchronizers within Structure.|
The cycle guard is a component that detects conflicting synchronizers and prevents them from cycling forever, overriding each other's changes. The table below describes the system properties that control the cycle guard.
|Set to |
|The maximum number of times that a synchronizer is allowed to run, processing the changes generated by another synchronizer. If this limit is exceeded, the two synchronizers are considered to be in conflict.|
The minimum number of times a cycle must be detected for a synchronizer before an e-mail notification about that synchronizer is sent to JIRA administrators.
The counter is reset when a synchronizer is automatically disabled, so if this number is greater than 1 and automatic disabling is on, the administrators will not be notified.