Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

JIRA rounds 'updated' date differently across different REST APIs

Jira v8.5.7


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:

expand: "names,schema",
startAt: 0,
maxResults: 1000,
total: 1,
issues: [
expand: "operations,versionedRepresentations,editmeta,changelog,renderedFields",
id: "139745",
self: "",
key: "CBSE-8965",
fields: {
updated: "2020-10-08T16:42:27.000-0500"

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:

Then 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

1 answer

1 accepted

0 votes
Answer accepted
Andy Heinzer
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Oct 09, 2020

Hi Perry,

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.


Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events