The xApps library is a core component of the JWT app.
Please do not delete this app unless you want to uninstall JWT completely or unless instructed to do so by our support team.
Workflow configuration
We continuously improve JWT and the user experience. As part of this process, workflow functions will be replaced with better and more efficient alternatives.
In this process JWT functions might get deprecated. Deprecated functions, as of today, continue to work but cannot be selected anymore. Existing deprecated functions can, however, be updated.
If you choose to re-configure a deprecated function, you can enable this feature here.
It is highly recommended to deprecated functions alternative functions. Alternatives are listed on the dedicated function overview pages.
Remote actions
A remote action can reach any URL you configure in a connection. To make sure this cannot be used to reach services that were never meant to be reachable from the outside, JWT blocks connections pointing to internal or private addresses SINCE 3.5.11
This kind of attack is known as server-side request forgery (SSRF). The protection is active by default.
Enable Allow internal addresses if you want to connect to a service inside your own network, such as a self-hosted Confluence, an internal REST API, or a service running next to Jira.
When enabled, remote connections and remote actions may target internal or private addresses, for example 127.0.0.1, 10.x.x.x or 169.254.169.254. Leave this off unless you have a specific need to call an internal service.
Only allow internal addresses if you trust every user who is able to create or edit a connection! Once enabled, anyone who can configure a connection can make your Jira node send requests to any host it can reach, including internal administration interfaces.
Two checks are always enforced and are not affected by this setting:
-
the base URL must use HTTP or HTTPS and the host must be resolvable
-
Jira's outbound allowlist is always respected
If the setting cannot be read, internal addresses stay blocked.
Learn more about the ranges that are blocked
Language configuration
You can globally define the rendering language for JWT. The rendering language defines which value will be returned when inserting field codes for system fields that possibly have been translated by a Jira administrator.
The following field codes are affected:
Changing the rendering language will break all expressions that reference system field values that can be natively translated.
|
Expression |
Default |
With translation |
|---|---|---|
|
Bash
|
This logical expression might pass, if the status name is Open in the Jira default language (e.g. English). |
This logical expression might fail if the rendering language was updated and the translated name differs from Open (e.g "Offen" in German) |
|
Bash
|
This expression will only return linked Bugs. |
This expression might not return results, if the issue type name was |
Bundled versions
Each version of Jira Workflow Toolbox comes with a specific version of the xApps library. It is recommended to use these combinations only.
The respective Jira compatibility of a xApps library version is determined by the corresponding Jira Workflow Toolbox version.
|
JWT version |
xApps library version |
|---|---|
|
3.5.11 |
1.5.9 |
|
3.0.0 |
1.1.0 |
|
2.9.3 |
1.0.24 |
|
2.9.2 |
1.0.23 |
|
2.9.1 |
1.0.22 |
|
2.9.0 |
1.0.21 |