Issue Summary

Product Affected: Atlassian Access

Where: Audit logs.

Using admin api, the Access audit log contains two different time format, one with subsecond, one without subsecond.

Example:
2023-02-11T01:03:54.002Z Atlassian Internal System Added xxxxx.com domain to verify
2023-02-11T01:03:54Z Atlassian Internal System Changed authentication policy Users in yyyy.com for domain xxxxx.com

This is reproducible on Data Center: (yes) / (no)
yes

Steps to Reproduce

Just need to use the Admin apis.

https://hello.atlassian.net/compass/component/c99c9c0c-e227-49ac-8c3d-76058d4e2a20/app/b%3AYXJpOmNsb3VkOmVjb3N5c3RlbTo6ZXh0ZW5zaW9uLzIzZDBiMGEyLTU4OTctNDYxOC1iYjU4LTg5MjQ0NmU1MWMyZi9jYjcxNzQ4Yy0yNGY1LTQ1ZDEtYjVkYS01NTg3NDM2ZDU1NDcvc3RhdGljL3BfX3BhbmVscw%3D%3D?extensionPath=panels%2Faudit-log-viewer-support&env=prod-east&chromeless=1&utm_source=compass&utm_medium=compass&utm_campaign=compass

2023-02-09T19:51:14Z atlassian-internal-system

Expected Results

Expected behavior:

2023-02-11T01:03:54.002Z
2023-02-11T01:03:54.000Z

Actual Results

How it is showing:
2023-02-11T01:03:54.002Z
2023-02-11T01:03:54Z

Workaround

No workaround.
Jira already fixed that in the past.
https://atlassian.slack.com/archives/C02TETUTW3C/p1676320088758139