Child pages
  • Advanced Configuration with System Properties

This documentation relates to an older version 2.8 of the Structure Plugin for JIRA. View the current documentation home.

Skip to end of metadata
Go to start of metadata

Certain advanced aspects of Structure's behavior might not have dedicated configuration pages, being controlled by system properties instead. This page lists Structure-related system properties and describes how to set them.

Setting System Properties on Startup

You can set a system property 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.

Setting System Properties with Script Runner

If you don't want to restart JIRA, you may use the free Script Runner add-on to set system properties.

  1. Install Script Runner.
  2. Go to Administration | Add-Ons | Script Runner | Script Console.
  3. Select Groovy as the Script Engine.
  4. Enter the following code into the Script text box, adjust property name and value as needed, and click Run Now.
System.setProperty("", "5")

The changes take effect immediately, but the properties will be reset to their default values when you restart JIRA. If you want the changes to be permanent, please use the -D startup option as described above.

Synchronizer Cycle Guard

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 true to disable the cycle guard. Conflicting synchronizers will not be prevented from running forever. Not recommended.
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.
If true, conflicting synchronizers will not be disabled automatically. The cycling may repeat after a user-generated change.
If true, the cycle guard will never send e-mail notifications to synchronizer owners.
If true, the cycle guard will never send e-mail notifications to JIRA administrators.

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.

  • No labels