Performance Settings

JWT is a powerful tool that can handle a lot of you Jira data!

But the more data you have on your instance, JWT might impact the overall performance once you have configured complex calculations.

To stay on top of Jira's performance, you can easily restrict JWT's CPU and memory usage!

You can define the maximum execution time of each JWT part individually.

All values are in seconds. If a calculation takes longer as the specified value, the below written rules will apply.

You can also disable the execution limit for each part. If you do so, you might experience performance issues!

It is recommended to not turn off the execution limits!

Area	Default value	Configuration
Automation rules	10s	If the underlying calculation for a rule takes longer than the defined value or has reached the memory usage (see below) it will abort the whole calculation without returning a result and an error will be thrown. Information about the error will be written to the Jira log.
Calculated fields	10s	If the underlying calculation for the field takes longer than the defined value or has reached the memory usage (see below) it will abort the whole calculation without returning a result and an error will be thrown. Information about the error will be written to the Jira log.
JQL functions	10s	If the underlying calculation for a JQL function takes longer than the defined value or has reached the memory usage (see below) or has reached the subquery limit (see below) it will abort the calculation. Only issues calculated at this point will be returned In addition, an error will be displayed in the Issue navigator. Information about the error will be written to the Jira log.
Workflow functions	10s	If the underlying calculation for the workflow function (condition, validator, post function) takes longer than the defined value or has reached the memory usage (see below) it will abort the whole calculation without returning a result and an error will be thrown. Information about the error will be written to the Jira log.

In addition to time limits, you can define the number of issues that should be processed in a single calculation.

In order to save resources, you can set a limit for issues to be processed in a single parser function.

The default value is 50.000.

Used for JWT JQL functions where you can define a JQL subquery, such as:

Setting a limit will only limit the number of issues returned by the subquery, not by entire JQL function itself.

The default value is 1.000.

If you still have questions, feel free to refer to our support team.