Are you using JQL Search Extensions for Jira Server/Data Center and want to continue using JQL Search Extensions on Jira Cloud? This page describes the key platform and feature differences. You can also find a list of the additional Cloud-only extensions that are available to you with JQl Search Extensions for Jira Cloud.
In On this sectionpage:
|
Platform differences
JQL syntax
The implementation of JQL Search Extensions is different for Jira Server/Data Center and Jira Cloud.
...
For Jira Cloud, most JQL extensions are implemented as JQL keywords as references to issue metadata resulting in indexed searches. Keywords are followed by operators, for example, commentedOnDate < "2018-05-26". Other, more complex searches are implemented as JQL functions.
Usage
In JQL Search Extensions for Jira Server/Data Center, you can use the extensions in Jira’s advanced search.
In JQL Search Extensions for Jira Cloud, JQL keywords provided by the app can be used in Jira’s advanced search and the Extended Search page. JQL functions are accessible from the Extended Search page or by using Extended Search filters in Jira advanced search.
Examples
Jira Server/ Data Center |
|---|
 |
Jira Cloud |
 |
Execution model
With the Server/Data Center version, the search queries are executed in the same Java Virtual Machine (JVM) as Jira. In the Cloud version, the JQL Search Extensions service is a separate deployment communicating with Jira over the REST API. As a result, all operations in the cloud are indexed asynchronously, and updates to issues in Jira can be reflected in the JQL with a slight delay.
Migration pathway
Queries are not migrated. If you want to use any saved queries from your Server/Data instance in Jira Cloud, the first step is to identify queries that use JQL Search Extensions. You should especially look at:
filtersFilters
board Board filters
automation Automation rules
dashboard Dashboard gadgets
plugins Other apps that accept filters and JQL queries (e.g. JSU, JMWE, Power Scripts, BigPicture)
Once you have identified where the saved queries are used, translate them to the Cloud-equivalent JQL extension using the table below. You can also build new queries using the additional extensions provided by JQL Search Extensions for Jira Cloud. If you need further guidance, contact our support team.
Feature parity comparison
The table below lists the parity between JQL Search Extensions for Jira Server/Data Center and Jira Cloud. Note the difference in syntax for Server/Data Center functions and Cloud keywords.
Server/Data Center | Cloud | Notes |
|---|---|---|
Projects | ||
movedIssues() |
| |
Fields | ||
fieldMatch() |
| |
fieldsHaveSameValue() |
| Limited support at the moment but a generic function is on our roadmap |
Attachments | ||
attachedAfter() |
| |
attachedBefore() |
| |
attachedBetween() |
| |
attachedOnDate() |
| |
attachedByUser() |
| |
attachmentExtension() |
| |
attachmentName() |
| |
attachmentsCountEqualTo() |
| |
attachmentsCountGreaterThan() |
| |
attachmentsCountLessThan() |
| |
Comments | ||
commentedAfter() |
| |
commentedBefore() |
| |
commentedBetween() |
| |
commentedOnDate() |
| |
commentedByUser() |
| |
commentsCountEqualTo() |
| |
commentsCountGreaterThan() |
| |
commentsCountLessThan() |
| |
Versions | ||
affectedVersionsArchivedCountLessThan() |
| |
affectedVersionsArchivedCountEqualTo() |
| |
affectedVersionsArchivedCountGreaterThan() |
| |
affectedVersionsCountLessThan() |
| |
affectedVersionsCountEqualTo() |
| |
affectedVersionsCountGreaterThan() |
| |
affectedVersionsOpenedCountLessThan() |
| |
affectedVersionsOpenedCountEqualTo() |
| |
affectedVersionsOpenedCountGreaterThan() |
| |
affectedVersionsReleasedCountLessThan() |
| |
affectedVersionsReleasedCountEqualTo() |
| |
affectedVersionsReleasedCountGreaterThan() |
| |
affectedVersionReleasedOnDate() |
| |
affectedVersionReleasedBetweenDates() |
| |
affectedVersionReleasedAfterDate() |
| |
affectedVersionReleasedBeforeDate() |
| |
fixVersionsArchivedCountLessThan() |
| |
fixVersionsArchivedCountEqualTo() |
| |
fixVersionsArchivedCountGreaterThan() |
| |
fixVersionsCountLessThan() |
| |
fixVersionsCountEqualTo() |
| |
fixVersionsCountGreaterThan() |
| |
fixVersionsOpenedCountLessThan() |
| |
fixVersionsOpenedCountEqualTo() |
| |
fixVersionsOpenedCountGreaterThan() |
| |
fixVersionsReleasedCountLessThan() |
| |
fixVersionsReleasedCountEqualTo() |
| |
fixVersionsReleasedCountGreaterThan() |
| |
fixVersionReleasedOnDate() |
| |
fixVersionReleasedBetweenDates() |
| |
fixVersionReleasedAfterDate() |
| |
fixVersionReleasedBeforeDate() |
| |
latestReleaseVersionForProject() | No direct cloud equivalent at the moment | |
Links | ||
linksCountLessThan() |
| |
linksCountGreaterThan() |
| |
linksCountEqualTo() |
| |
linkedBy([linktype], jql-query or issuekeys) | function | |
links(jql-query, link type) | function | |
linksIssue() |
| |
linkType() |
| |
linkedIssueStatus() |
| |
linkedIssueStatusCategory() |
| |
linkedIssueType() |
| |
linkedIssuePriority() |
| |
linkedByIssueProject() |
| |
Issue Updates | ||
updatedByUserCountLessThan() |
| |
updatedByUserCountGreaterThan() |
| |
updatedByUserCountEqualTo() |
| |
updatedByUser() |
| |
transitionedByUser() |
| |
loggedTimeByUser() |
| |
Subtasks | ||
subTaskOf(jql-query) | function | |
parentOf(jql-query) | functions
| |
subtaskCountLessThan() |
| |
subtaskCountGreaterThan() |
| |
subtaskCountEqualTo() |
| |
subTaskKey() |
| |
subtaskPriority() |
| |
subTaskType() |
| |
subTaskStatus() |
| |
subTaskStatusCategory() |
| |
Software development | ||
openPullRequestsCount() | There is no support in JQL Search Extensions | If you linked your development tools, refer to the native Jira Cloud JQL documentation https://confluence.atlassian.com/jirasoftwareserver/advanced-searching-development-fields-reference-973491363.html |
Issue hierarchy | ||
allIssuesInEpic(jql-query or issuekey) | function | |
epicOf(jql-query) | function | |
User | ||
| No direct cloud equivalent | |
Cloud-only features
JQL Search Extensions for Jira Cloud provides the following additional extensions unavailable with the Server/Data Center app.
...