Fixing Filters Affected by the 1 October 2026 Bug

Learn how to identify and correct Jira Enhanced Search filters affected by the 1 October 2026 bug, or remove filters that are no longer needed.

If you have been affected by this bug, you will receive an email and in-app messaging later this month with specific filter IDs that were affected. This bug affected very few (less than 0.5%) customers.

On 1 October 2026, we identified a bug that had inadvertently been introduced into Enhanced Search for Jira and ScriptRunner for Jira Cloud. This bug caused a small set of Enhanced Search filters to stop working as intended.

Most of the affected filters have now been fixed; however, there are some filters that require a manual update. These filters may be showing outdated information as they are not syncing automatically.

Please either remove the filter if it is no longer needed, or manually correct the query using this guide for instructions.

1. Locate each Jira filter using the filter ID/Atlassian account ID we have sent you. You can do this by searching for the filter https://<insert_instance_name>.atlassian.net/issues/?filter=<insert_filter_id>

2. Check the Jira filter description.

3. Confirm if the Jira filter description contains the correct Enhanced Search filter query, and respond back to us with this query and the associated Jira filter ID, so we can manually fix the filter.

4. If it is not the correct filter query, respond back to us with the desired filter query and the associated Jira filter ID, so we can manually fix the filter in our database.

5. If the filter is an Enhanced Search filter but is no longer required, please navigate to the Enhanced Search page, and delete the Enhanced Search filter.

   If the filter was never an Enhanced Search filter, then you can ignore and skip it.

If you are affected and have more questions or need help, please contact support.