Date time fields with Time Ago preference, display abbreviated

[Mark Roethof]

Hi all,

When having the "Date/time" user preference set to "Time Ago", on Service Portal, lists in the Platform UI, etc., date/time fields are shown with "1mo ago", "2y ago", etc.. Instead of "1 month ago".

We are encountering this on our upgraded dev environment, which is on New York patch 2. Also verified now on my Personal Developer Instance which is on New York patch 2.

Does this sound familiar to anyone? Might this for example just be a system property which is controlling this behavior?

See for example below screenshots. Interesting behavior notable: after a screen refresh, shortly "2 weeks ago", "1 hour ago", etc. is shown, and then this changes to "20d ago", "2y ago", etc..

Kind regards,
Mark

---

LinkedIn
Community article list

[Harsh Vardhan]

i checked on my PDI and it's on patch 2 , i did not find the issue. 

can you please confirm the date format in the properties "glide.sys.date_format" , try to set in below format 

yyyy-MM-dd. 

just  try and clear the cache and see if its working or not.

[Mark Roethof]

Did try the caching. The date format doesn't make sense to look at. It does appears consequent when using non-English plugin, in our case Dutch. Somehow shortly the full text, and after split second (so client side) abbreviated.

I just also opened a case for this. Maybe it's just a simple setting, though somehow this changed between Madrid and New York.

Kind regards,
Mark

[Mark Roethof · Accepted solution]

Received update from HI, they're not going to fix this.

Most Probable Cause:

This is a known issue within the ServiceNow platform. I created PRB - PRB1371356 - for this issue.

Solution Proposed:

The development team reviewed the PRB - PRB1371356 - that i created requesting the development team to look into this issue for us. After careful consideration, the development team have decided that they Won't Fix this issue. The Development Team has decided to close 'PRB' for now, as they have declared that this problem is not prioritized high enough to be fixed in the near future. I am aware this may cause frustration since this is a confirmed Product Defect that you would expect to be solved. If solving 'PRB' is of high priority for you, please let us know the business impact. From there we can present your case back to the Development Team in an attempt to have them reconsider their decision. Otherwise, if you are willing to accept the Development Team's decision, you are welcome to accept the solution and close this incident. Apologies for the inconvenience caused in this regard. Please let us know your response and I can take it forward from there.