Issue Summary

Once automation is triggered and the audit log records this run, timestamps are saved according to the browser timezone and ignore any configuration made in the instance default timezone or user AA account timezone preferences.

Steps to Reproduce

1. Trigger an automation rule.
2. Check both account and instance timezone config.
3. Change the Atlassian account timezone https://id.atlassian.com/manage-profile/account-preferences?ref=jira&src=personalsettings

Expected Results

Timestamps being updated according to the AA preferences and match the timestamp in the issue history.

Actual Results

Automation rule audit log timestamps stay the same no matter the configuration change regarding the timezone preferences.
Note
Changing the Instance timezone from jira/settings/system/general-configuration also results in the same behavior

Workaround

Currently, there is no known workaround for this behavior. A workaround will be added here when available.