Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Since version 6.3.0 (for Jira 7) and 7.1.0 . We (for Jira 8), we have removed the ability to configure the connectionConnection's cache expiry via the connection user interface to give way to the new Atlassian cache2 library upgrade to support Data Center.Image RemovedConnection Configuration Interface.

...

The cache expiry will have defaulted now defaults to 24 hours. If you need to configure the cache expiry for some reason. You still can any reason, you may still do it by configuring the System Property(

...

system property (you must be an admin).

To do this: 

  1. Edit bin/setenv.sh
     

  2. Append the following property to JVM_EXTRA_ARGS:

Code Block
-Dnet.customware.plugins.connector.salesforce.connection.<connectionId>.cacheExpiry

...

=30

Replace the <connectionId> placeholder with the Connection that you are configuring.

In the above example, the value 30 represents 30 minutes. You may adjust this accordingly.

(warning) If you are administering Jira Data Center, you will need to restart the Jira Data Center Cluster(Stop cluster (i.e., stop all the nodes in the cluster) for the cluster caches to pick up the new configuration.