You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
It appears that the date/time returned from a JQL search to the REST API differs from the date/time returned from the issue directly:
Using the REST API to search:
The result is:
See that the 'updated' field is
"2020-10-08T16:42:27.000-0500"However, if I use the REST API to fetch the full document contents:
https://issues.couchbase.com/rest/api/latest/issue/CBSE-8965Then the return 'updated' field is:
updated: "2020-10-08T16:42:27.259-0500"So it would seem that JIRA is rounding the date in different places
Thanks for pointing out this problem. I can see how this difference could cause confusion. I found that this has already been documented as a bug back in JRASERVER-28238. I have updated this bug so that it is more in line with our standards.
Sorry to report that there does not appear to be a clear workaround for this. However I suspect this has been prioritized low because Jira never displays date/times to this level of precision within the UI. That said, I didn't expect the values to be different here between these two calls.
When Jira is searching for issues, it has to rely upon the indexes created for these issues. Jira uses Lucene to do this. I suspect that in order to optimize the search indexes, these millisecond values might be getting dropped from the actual value when the indexes are created.
I hope this helps.