Release Notes
August 2023
Notice of Deprecated JQL Keywords
We've identified a few keywords that are either not functioning as expected or already have their use cases covered by Jira Search. As a result, the following keywords will be removed on 1 November 2023:
hasLinks
commentVisibleGroup
commentVisibleRole
worklogVisibleRole
worklogVisibleGroup
You should review any queries related to these and change them accordingly. For example, you could use issueLinkType
(which is provided by Atlassian here) in queries where you currently use hasLinks
to search for issues based on the type of issue links you have.
July 2023
Atlassian JQL Bug Affecting Assignees
Atlassian is currently aware of a bug that affects assignee in (...)
when used with display names. This bug can cause inconsistent results when the JQL is executed within an Enhanced Search query.
Atlassian is working on a fix for this bug, but there is no ETA for the release. In the meantime, you can use account IDs instead of display names in your JQL queries as a workaround.
For example, instead of assignee in ('John Doe', 'Jane Doe')
, use assignee in (1234567890, 9876543210)
.
May 2023
We are currently carrying out some performance-related maintenance work on the Enhanced Search for Jira Cloud app. As a result, licences that have been inactive since before 4 April 2023 may lose any saved filters and other preferences. To mitigate this and ensure that saved functions and filters continue to work, you will need to reactivate your license as follows:
- Reinstall as an admin.
- Ensure you have filter syncing turned on.
- Update an issue on your instance (you may reverse the change if required).
Moving to DynamoDB has helped improve the overall performance of Enhanced Search. As part of the move to DynamoDB we migrated ES users with active licences and their user properties. Users with inactive licences were not migrated. We would like to clean up the codebase by removing userProperty references and ensuring we remove unused code in the codebase.