Unable to sync some filters due to change in behaviour of the "approximateLastUsed" property

Atlassian are in the process of rolling out a bug fix, which is expected to complete by the end of 29th April.

In the meantime, if you experience issues with filters not syncing automatically, you can manually trigger a filter synchronisation in the Enhanced Search app.

Atlassian has started rolling out a bugfix for this issue. We will continue to monitor the situation and provide updates once the rollout is completed.

Atlassian found a bug that was preventing the last used timestamp in Jira filters to be properly updated, and a fix should be deployed next week.

After releasing another potential fix, we are still observing an unusually high number of filter syncing timeouts. As our process relies on filter data provided by Jira for optimization, we are currently unable to implement an immediate alternative solution. To move forward, we are actively seeking further information from Atlassian to better understand the scope of the recent changes.

We appreciate your patience while we continue to investigate this matter. In the meantime, please remember that you can manually sync filters via the Enhanced Search page to obtain up-to-date results as a temporary workaround.

We are seeing a higher number of filter syncing timeouts than before this incident was declared. We are investigating whether this is expected based on the increased number of filters that we are now syncing.

We can see that filter syncing is operating again in all products in all regions. We were relying on data for when a filter was last used in Jira that is no longer being populated as expected. We have released a fix for this which means we will be syncing some filters that have not been used for over 30 days, where we were not syncing these before. We are seeing a small increase in the number of filters that are timing out during syncing in ScriptRunner Enhanced Search in both EU and US regions. If you notice this incident is affecting you, please contact our support so we can look into the specific circumstances of your instance and filters.

Operations seem to be proceeding as expected so far. However, to ensure a complete resolution with an effective fix, we are awaiting further details from Atlassian about these recent changes that may impact our filter syncing process.

We appreciate your patience as we continue to monitor this issue.

After rolling back the recent changes to the jql-sync-scheduler repository, we are noticing an uptick in the number of filter sync requests. Consequently, you might experience a higher-than-usual volume of requests, as the system works to address the backlog.

We appreciate your patience and understanding as we continue to monitor and resolve this issue.

The filter syncing failures mentioned in the last update are related to the latest changes that have been recently deployed in the jql-sync-scheduler repository.

Upon further investigation, we have found out that all filter syncing is failing since 15:46 UTC.

We have identified a change in a property we rely on to determine whether we need to sync filters or not. This is only affecting some customers, and your saved Enhanced Search filters may be showing out of date results.

We have identified a potential solution to fix the issue, which is currently being deployed to production.

As a workaround until the fix has been deployed, you can manually sync the filters via the Enhanced Search page to get up to date results.

We have identified a change in a property we rely on to determine whether we need to sync filters or not. This is only affecting some customers, and we are currently investigating how many are affected. Your saved Enhanced Search filters may be showing out of date results.

As a workaround, you can manually sync the filters via the Enhanced Search page to get up to date results. Apologies for the inconvenience.