Why are comment timestamps and SLA metrics in Jira Cloud intermittently showing incorrect times desp

[Hari krishna]

We are experiencing a recurring and inconsistent issue in our Jira Cloud instance where comment timestamps and SLA timings are not displaying the correct local time (Asia/Kolkata), even though:

• All users have their profile time zones set correctly to Asia/Kolkata

• The SLA calendar is configured properly with defined working hours (Mon–Fri, 9 AM–6 PM)

• No VPN is being used

• System and browser times are verified as correct

• Users are from the same region, not remote

• The issue is affecting multiple users across different projects

• Comments are manually added (not from automation)

Issue Pattern:

• The issue started about a week ago

• Initially appeared for a few hours, then disappeared

• Came back again on Friday, resolved itself, and then reappeared the next morning

• Currently, Resolved again

• The timestamps shown (e.g., 7:30 AM) are earlier than the actual comment time

We’ve tried clearing browser cache, tested in incognito, and on different browsers – the problem still persists.

[Alina Kurinna _SaaSJet_]

Hi @Hari krishna 

Thanks for providing all those detailed observations; it really helps narrow things down.

What you're describing sounds like it could be a temporary backend issue on Atlassian’s side. Since this is affecting multiple users, projects, and browsers, and the issue resolves and reappears randomly, it could indeed be internal.

In the meantime, if you’re looking for a more reliable and transparent way to track and analyze SLA timings, especially across teams and time zones, our team has built a solution that might help: SLA Time and Report for Jira.

With it, you can:

• Precisely configure and monitor SLA timers for different conditions
• Track elapsed and remaining SLA time directly in the issue view
• Get clear, real-time SLA progress with visual indicators
• Filter, analyze, and export SLA reports across assignees, teams, and services
• Set up alerts and automatic actions (e.g., reassign, change priority) when SLAs are about to breach

It can simplify your SLA tracking significantly and give you deeper visibility than the built-in features.

Let me know if you'd like to explore it or have any other questions!

[Marc - Devoteam]

Hi @Hari krishna 

Welcome to the community.

What is the default timezone set in Jira and the calendar(s) used on the SLA itself, what is the time zone set there?

[Hari krishna]

Hi @Marc - Devoteam ,

Thanks for your response,

This was an internal bug in jira, now they have resolved the bug.
Thanks,
Hari