Time stamp minutes shown incorrectly in Customer Portal (always :09?

Question

Hello Community,

we are encountering a strange issue in Jira Service Management:

In the Agent view, when adding or viewing comments on a ticket, the timestamp shows the correct hour and minutes.

But in the public Customer Portal view, the minutes part is wrong. In some tickets it shows “:06”, in others “:07” or “:09” – but never the correct value.

Example:
A ticket was created at 10:35, and an agent added a comment at 10:40.
In the Agent view, the comment correctly shows as 10:40.
In the Customer Portal view, the same comment is shown as 10:09 – which makes it look as if the comment was created before the ticket itself existed.

Has anyone else observed this behavior or something similar?
Is there a known solution or settings that might cause this?

Thank you for any insight

Customer view:

Agent view:

Sven_g7sk34 · Answer

Hi @Dan Breyen,

thank you for your reply and for pointing me to those tickets.

I just wanted to confirm that the issue is reproducible for me in Edge, Chrome, and Firefox.
It also occurs when switching between German and English language settings.

So unfortunately it doesn’t seem to be related to a specific browser or language pack.

Thanks again for looping in Atlassian Support – I’ll keep an eye on their feedback.

Dan Breyen · Answer

Hi @Sven I'm not seeing that behavior in my portal.  Just to eliminate variables, have you tried another browsers?  Do other users experience the same behavior?  It appears you using German for the Language Pack.  I'm wondering if that is contributing to the issue.  One thing to possibly try would be to try another language pack.

In Atlassian's Jira Site I found JSDCLOUD-2353 and JSDCLOUD-16787  which might be involved, as they have to do with displaying dates in the portal.

I'm going to loop Atlassian Support into this for further evaluation. I would suggest if you don't hear back in a few days to have your System Administrator open a Work Item with them to continue to investigate this issue.

Hope that helps.