Exalate Incident History

The proxy user name was reverted back to Exalate. We are considering the incident as resolved.

We are actively working with Atlassian support to determine the best resolution for this issue as soon as possible. We will be providing the next update within 6 hours or as soon as we have any relevant information.

We are actively working with Atlassian support to determine the best resolution for this issue as soon as possible.

We continue to investigate the best approach to solve this issue with the help of Atlassian support.

Following up on an unadverted change in the application name which causes the proxy user to be shown with the full name of the application instead of just "Exalate". This is already notified to Atlassian and we are awaiting the required action on their end to revert the change. Impact: Updates made by Exalate will display "Exalate Classic Connector for Jira (Two-way Sync)" as the user making the change.

After close monitoring, the issue is considered as fully resolved. We will be posting a RCA here in due course.

All nodes are back to normal operation. We continue to monitor the situation closely.

The restart is still in progress and is going without any issues. We will update you as soon as it is completed.

The rolling restart of the nodes is in progress. You will experience a brief restart on JCloud nodes. We will keep you posted with our progress.

We will be actioning a change on Exalate Cloud to improve stability. The impact on your node will be that limited to a restart with the node being unavailable for a couple of min. The inconvenience is regretted.

Some Jira Cloud nodes are experiencing instability over the past 30mins. The problem is limited and only affects some customers. We will be providing an update shortly.

The deployment was completed successfully and the issue reported stands fully resolved. A detailed RCA will be published in due course.

The deployment continues uninterrupted. We will update you in due course as soon as it is fully completed.

The deployment of the hotfix: Exalate Classic 5.35.4 - Jira Cloud, in underway (https://community.exalate.com/t/jira-cloud-version-5-35-4/8215). The deployment is being closely monitored for any anomalies. We will update you in an hour.

The QA and testing is taking slightly longer than expected, but we expect to start the deployment within the next hour. We will update you before starting this.

We are still on course for the patch deployment and the release is going through additional QA validation now (required for a full production deployment). We expect to have the next update within an hour.

We have deployed the fix to a few select customers and validated results further. The mass rollout is being planned right now. We will update you within the next hour about progress.

The fix is ready and we are working on the deployment approach with minimal impact for customers. It will be systematically rolled out to all clients. We will provide an update in the next hour about the deployment.

We are still testing the fix and results are still good. We are close to finalizing it. Next update will be within the hour.

The new fix has been created and initial tests are promising. We are deep in QA with the new fix and will provide an update within the hour about the results. The inconvenience is regretted.

Unfortunately, the testing of the fix revealed an unexpected issue and we are now fine tuning the fix in order ensure that it incorporates all possible use cases. We will have an update for you in an hour.

The fix is currently being validated to find the best approach forward. We will provide another update within the hour.

The root cause has been identified and we are working on a fix. Please expect another update within an hour.

We continue to investigate this issue with our engineers to determine the root cause.

We've received multiple reports of syncs looping after update to the new Jira Cloud forge app. Our initial investigation leads us to believe this is happening due to the change in the Proxy User account. We are actively working on determining the root cause and applying a fix.