We made improvements in how application matches text with * operator in Data Center and Server.

We made improvements in how application matches text with * operator in Data Center and Server.

We made improvements in how application matches text with * operator in Data Center and Server.

This release contains performance improvement to the allIssuesInEpic search function.

This version contains performance improvement to the allIssuesInEpic search function.

Contains a fix for fieldMatch function. The function was failing for some missing issue fields.

Contains a fix for fieldMatch function. The function was failing for some missing issue fields.

This release is to fix the Atlassian Marketplace listing. There is no need to upgrade if you are using JQLSearch Extensions 3.1.3

This release is to fix the Atlassian Marketplace listing. There is no need to upgrade if you are using JQLSearch Extensions 3.1.3

This version contains improvements required to work with GDPR changes in Jira 8.4

This version contains improvements required to work with GDPR changes in Jira 8.4

- the error message will be shown in the UI when jira.search.maxclauses limit is reached

- the error message will be shown in the UI when jira.search.maxclauses limit is reached

- subqueries that are passed to functions are limited to 10000 issues by default (JQL warnings are displayed if the limit is exceeded)

- the limit is configurable with a new com.digitaltoucan.jqlextensions.subquery.limit system property

- subqueries that are passed to functions are limited to 10000 issues by default (JQL warnings are displayed if the limit is exceeded)

- the limit is configurable with a new com.digitaltoucan.jqlextensions.subquery.limit system property

- subqueries that are passed to functions are limited to 10000 issues by default (JQL warnings are displayed if the limit is exceeded)

- the limit is configurable with a new com.digitaltoucan.jqlextensions.subquery.limit system property

- subqueries that are passed to functions are limited to 10000 issues by default (JQL warnings are displayed if the limit is exceeded)

- the limit is configurable with a new com.digitaltoucan.jqlextensions.subquery.limit system property

- Fixes for SQL Server

- updatedByUserCount* functions support issues with 0 updates

- Fixes for SQL Server

- updatedByUserCount* functions support issues with 0 updates

- Fixes for SQL Server

- updatedByUserCount* functions support issues with 0 updates

- Fixes for SQL Server

- updatedByUserCount* functions support issues with 0 updates

Support for Data Center

Performance improvements for queries matching 1'000+ issues

Fixed subqueries for 10.000+ issues

New feature:

- movedIssues(projectKey) allowing to find issues which moved from the project in argument. For instance:

project = SEARCHSERVER AND issue in movedProject("SEARCHCLOUD")

Will find all issues which are in project SEARCHSERVER and moved from project SEARCHCLOUD.

Bugfixes:

- 10x memory decrease for large (above 1000 issues) nested queries

More improvements and bugfixes to wildcard operators

Fix for whitespaves in fieldmatch

Fixed searching for issues with 0 subtasks with the following functions:

- subtaskCountLessThan

- subtaskCountGreaterThan

- subtaskCountEqualTo

fieldsHaveSameValue(jql-subquery, field-name1, field-name2,...,field-name-x)

FieldsHaveSameValue can be used to find issues with fields having the same value. For instance:

issue in fieldsHaveSameValue("version", "my-custom-field-with-version")

It is possible to use multiple fields in the expression, such as below:

issue in fieldsHaveSameValue("version", "my-custom-field-with-version", "one-more-field-with-version")

It is also possible to add JQL subquery to the expression. It will narrow the search only to those issues which match the subquery (in the example below, are in the project DEMO and have the same value of fields version and my-custom-field-with-version).

issue in fieldsHaveSameValue("project = SEARCH", "version", "my-custom-field-with-version")

In case fields contain multiple values (for instance, there are many values of field version) the function will expect all values to be equal (but doesn't expect the same order).

fieldMatch(jql-subquery, field-name, regexp)

FieldMatch can be used to find issues with field matching the regular expression in the argument. For instance:

issue in fieldMatch("project = SEARCH", "description", "find issues mat*")

will find all issues with description field matching the regular expression find issues mat*.

The asterisk * matches any alphanumeric characters. It is also possible to use all regular expression constructs, such as

issue in fieldMatch("project = SEARCH", "description", "find issu[a-z]{2} mat*")

issue in fieldMatch("project = SEARCH", "my custom field", "f[a-z]{5}

This function can be used with any system or custom field.

For documentation of of regular expression constructs, please follow this link

https://jqlsearchextensions.atlassian.net/wiki/spaces/SEARCH/pages/30497099/JQL+Reference+Server#JQLReference(Server)-fieldMatch(jql-subquery,field-name,regexp)

UserMatch can be used to find issues with user fields matching the regular expression in the argument. For instance:

assignee in userMatch("danie*")

Will find all issues with assignee username matching the regular expression danie*, such as daniel, danied, danie3 etc.

The asterisk '*' matches any alphanumeric characters. It is also possible to use all regular expression constructs, such as

assignee in userMatch("danie[a-z]") // matching danie followed by a single lowercase alphabet character

assignee in userMatch("dan[a-z]{3}") // matching dan followed by three lowercase alphabet characters

This function can be used for any user field. For documentation of of regular expression constructs, please follow this link

- Compatibility with Jira 7.10.x.

- membersof support for JQL functions with users

- performance optimisation for dates and counts

The plugin jar in release 1.4.2 was got corrupted during upload. This version is just a re-upload of the same functionality.

This version contains fixes and improvements to link related functions, until now:

• linkedBy
• links
• linksIssue
• linkedIssueStatus
• linkedIssueStatusCategory
• linkedIssuePriority
• linkedByIssueProject

in results also included subtasks and epics (internally in Jira data structure those relations are represented as links). This behaviour was confusing to most users as they expected to find issues with manually created links (such as "is blocked by" or "relates to"). To avoid further confusion we decided to fix this issue and since this version, all JQL functions mentioned above will return only issues linked manually.

To make link related searches more convenient we extended "linkedBy" and "links" functions to accept a link type name (one or many) that will be taken into account while searching, for example now you can search:

issue in linkedBy("project = ABC", "is blocked by", "relates to")

and this will return all issues that are blocked by or are related to a least one issue in ABC project.

Improve indexing mechanism to split long indexing runs into multiple background job calls to reduce transaction impact on database. This should result in lower database load after plugin installation.

Find all epics which have stories matching JQL query, for instance:

- issue in epicOf('resolution is empty') - finding all epics with issues without a resolution

or

- issue in epicOf('fixVersion = 1.0 and issuetype = Story')

This version includes performance improvements to issue indexing which has a significant impact in initial indexing time on instances with many issues.

Possibility to find issues which link issues matching JQL query. For instance:

- issue in links("project = JQLEXTENSIONS") - finds all issues which link issues in project JQLEXTENSIONS

- documentation

Possibility to find issues which are linked by issues matching JQL query. For instance:

- issue in linkedBy("project = JQLEXTENSIONS") - finds all issues which are linked by issues from project JQLEXTENSIONS

- documentation

Finding the entire hierarchy of an issue, epics, its issues and subtasks.

Ability to find parents of subtasks matching JQL query - parentOf.

Ability to find subtasks of parents matching JQL quer - subtaskOf.

Compatibility with Jira 7.5

New features for epics

- bugsInEpicCount

- bugsInEpicToDoCount

- bugsInEpicInProgressCount

- bugsInEpicDoneCount

- storiesInEpicCount

- storiesInEpicToDoCount

- storiesInEpicInProgressCount

- storiesInEpicDoneCount

Improved indexing on large (over million issues) instances.

Added new UI for troubleshooting and some performance improvements

New JQL function for finding issues where the version is the latest released version from the project.

Added a new troubleshooting API

Enabled data-center compatibility for server add-on.