POST /rest/api/2/expression/evaluate
Evaluates a Jira expression and returns its value. The difference between this and eval is that this endpoint uses the enhanced search API when evaluating JQL queries. This API is eventually consistent, unlike the strongly consistent eval API. This allows for better performance and scalability. In addition, this API's response for JQL evaluation is based on a scrolling view (backed by a nextPageToken) instead of a paginated view (backed by startAt and totalCount).
This resource can be used to test Jira expressions that you plan to use elsewhere, or to fetch data in a flexible way. Consult the Jira expressions documentation for more details.
Context variables
The following context variables are available to Jira expressions evaluated by this resource. Their presence depends on various factors; usually you need to manually request them in the context object sent in the payload, but some of them are added automatically under certain conditions.
user(User): The current user. Always available and equal tonullif the request is anonymous.app(App): The Connect app that made the request. Available only for authenticated requests made by Connect apps (read more here: Authentication for Connect apps).issue(Issue): The current issue. Available only when the issue is provided in the request context object.issues(List of Issues): A collection of issues matching a JQL query. Available only when JQL is provided in the request context object.project(Project): The current project. Available only when the project is provided in the request context object.sprint(Sprint): The current sprint. Available only when the sprint is provided in the request context object.board(Board): The current board. Available only when the board is provided in the request context object.serviceDesk(ServiceDesk): The current service desk. Available only when the service desk is provided in the request context object.customerRequest(CustomerRequest): The current customer request. Available only when the customer request is provided in the request context object.
In addition, you can pass custom context variables along with their types. You can then access them from the Jira expression by key. You can use the following variables in a custom context:
user: A user specified as an Atlassian account ID.issue: An issue specified by ID or key. All the fields of the issue object are available in the Jira expression.json: A JSON object containing custom content.list: A JSON list ofuser,issue, orjsonvariable types.
This operation can be accessed anonymously.
Permissions required: None. However, an expression may return different results for different users depending on their permissions. For example, different users may see different comments on the same issue.
Permission to access Jira Software is required to access Jira Software context variables (board and sprint) or fields (for example, issue.sprint).
Servers
- https://your-domain.atlassian.net
Request headers
| Name | Type | Required | Description |
|---|---|---|---|
Content-Type |
String | Yes |
The media type of the request body.
Default value: "application/json" |
Query parameters
| Name | Type | Required | Description |
|---|---|---|---|
expand |
String | No |
Use expand to include additional information in the response. This parameter accepts |
Request body fields
| Name | Type | Required | Description |
|---|---|---|---|
expression |
String | Yes |
The Jira expression to evaluate. |
How to start integrating
- Add HTTP Task to your workflow definition.
- Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
- Click Test request to test run your request to the API and see the API's response.