Get started

Use case library

JWT expression editor

JWT expression parser functions

JWT workflow functions

JWT remote actions

JWT automation rules

JWT calculated fields

JWT calendars

JWT properties

JWT JQL functions

Cloud migration hub

Additional product info

Versions Compared

Old Version 12

changes.mady.by.user Jona Ittermann

Saved on

compared with

New Version Current

changes.mady.by.user Thorsten Letschert

Saved on

Key

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

Content Layout Macro


UI Text Box
sizemedium
typeinfo

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

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

However, on large instances, JWT can have an impact on the overall performance, especially when performing complex or unoptimized calculations.

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

Status
colourYellow
titleSince 3.1.4



UI Expand
titleMaximum execution time


UI Text Box
sizemedium
typetip

You can define the maximum execution time of each JWT part area 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! (warning)It is therefore not recommended to not turn off the execution limits!


AreaDefault valueConfiguration
Automation rules10s

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 fields10s

If the underlying calculation for the a 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 functions10s

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 issue navigator. Information about the error will be written to the Jira log.

Workflow functions10s

If the underlying calculation for the a 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.



UI Expand
titleMemory usage


UI Text Box
sizemedium
typetip

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

Memory usage

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

UI Text Box
typeinfo

The default value is 50.000.


JQL functions

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


UI Text Box
typeinfo

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.



Include Page
DECADIS:Contact support
DECADIS:Contact support