We've just fixed the issue(2 AUG 2023 7:50 AM UTC). The update date of the issue will no longer be changed.
Here's what happened: We updated the backend to ensure better stability on larger instances and transitioned to using a new API. However, the new API turned out to have compatibility issues with certain characters, such as emojis. As a result, data stopped updating for some settings. We explored several solutions to this problem. The initial solution we chose proved to be flawed as we discovered that in some cases, data was being updated within the issue itself - the "Updated" field. This behavior was not mentioned in the documentation and was not detected during testing. Currently, we are using an alternative solution that may be slower but avoids updating the "updated" field.
Unfortunately, in the cloud, we cannot restore the previous update date for the request.
We apologize for any inconvenience this may have caused. If you've encountered any issues due to this incident, please reach out to our support team, and we'll do our best to assist you as much as we can.