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!
Maximum execution time
You can define the maximum execution time of each JWT part individually.
All values are in seconds. If a calculation takes longer as the set value, xyz
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 underlaying calculation for a rule take longer than the defined value, it will abort the whole calculation and write an error to the Jira log. |
| Calculated fields | 10s | |
| JQL functions | 30s | |
| Workflow functions | 10s |
