Confluence ↔ Jira – Interoperability of regional time zones and date conversion

Confluence ↔ Jira – Interoperability of regional time zones and date conversion

Confluence stores all timestamps in UTC and renders them in the viewer’s timezone preference. The Date macro and Jira issue links both apply the current user’s timezone when displaying dates, but they do not retroactively adjust historical values when a user changes their timezone setting.

When a user switches time zones, the page history and linked Jira issue dates remain unchanged in the database, yet the web UI shows different local times. This can create inconsistencies between what is recorded in Confluence’s audit logs and what users see when revisiting old content.

The key unresolved question is whether there is a supported mechanism to audit or re‑render these historical dates after a timezone change, and if not, what custom approach could be used to maintain consistency across Confluence and Jira.

Specifically:

• Is there an API or configuration that triggers re‑rendering of historical timestamps when a user’s timezone preference changes?
• Can a plugin expose a method to audit mismatches between stored UTC values and rendered local times for both Confluence pages and linked Jira issues?
• What impact would such a re‑rendering process have on performance and data integrity in a large Confluence instance?