Introduction
Time to be creative!
A huge number of potential use cases can be addressed by using Jira expressions which is currently a Cloud Only feature provided by Atlassian. Jira expressions can be a powerful tool but they come with limitations.
To master Jira expressions we strongly recommend reading the information we condensed on this single page. Especially when it comes to the difference between Jira expressions the JWT for Jira Cloud parser expressions.
Time to be creative! A huge number of potential use cases can be addressed by using JIra expression which is currently a Cloud Only feature provided by Atlassian.
Heading Parameter Erklärung
TODO
| Parameter | Description |
|---|---|
| Jira expression | Enter plain text and optionally use field codes, e.g. issue.summary, to insert field values. The result of the Jira expression shall return true or false. |
| Evaluation test | Select an issue for the context of the evaluation of the given Jira expression. After clicking the "Evaluate"-Button the result of the evaluation is shown below in a message box. If the syntax of the Jira expression is wrong or the evaluation with the given context issue returns an error, an error box with the respective error is displayed in an error box below. |
Heading Related use cases
TODO
The configuration
Every workflow function consists of multiple configurable fields. Required fields are marked with a red asterisk (*) and are essential for the correct operation of the function.
The number of available fields depend on the function. Make sure to check out available virtual fields and field codes.
A potential configuration, which is also one of the built-in usage examples could look like this:
This example will create a sub-task under the current issue and set the assignee to the current user.
Getting started
Get started by trying out the example configurations provided out of the box
The following example configurations are currently available:
