Future Consideration

Match date format to user's location across Lucid

Related products:Lucidspark

Forum|Forum|1 year ago
March 6, 2025
19 replies
395 views

Please allow the date format to be customise to the user’s locale. There’s only one country that uses mm-dd-yyyy format so in an international context this is really confusing. I don’t want to have to keep wondering what the date means and this leading to confusion.

For me, if I was involved in a buying decision in buying Lucid then this would be a flat no from me at this point.

When importing from jira, the date will come through in ISO format, therefore there is no issue with Jira - the presentation layer is abstracted from the underlying format and codified through locale logic in Lucid.

Pinned Reply By Spencer Cowley

@CraigC We appreciate you sharing the feedback here. I can understand this is a frustrating experience that you are running into.

I see you have shared that the date format is showing up all throughout Lucid - thank you for that context. I’d love to see this fixed throughout the entire product but would also like to better understand where you’re experiencing this pain the most.

In the context of Jira Cards and your experience on the canvas with them, are there specific places you experience the pain the most? Is it when dates have been added to the card face? Or in usage in timelines?

Appreciate you taking the time to share the feedback - I’ve recorded it and we will keep it in mind as we look at prioritizing upcoming work.

Show previous replies

Ambar D

Lucid community team

Thank you @Misz for adding to this thread with your feedback here. I apologize for the frustration here, and I certainly understand why this is so important.

I appreciate you taking the time to let us know just how important this feature is to you and for showing support for this idea.

B

BlimeyBen

This missing core component (it should not be considered a “feature” as such) has been pointed out over several years with no action being taken.

Currently, any element in Lucid which displays a date, such as a card or a roadmap timeline, has the potential to create significant confusion when shared among international users, which significantly limits the useability of Lucid products. A date displayed in the MM/DD/YYYY format with no option for localisation can be interpreted as two possible dates, depending on where the user lives. It looks sloppy, meaning I tend not to share my timelines with customers.

What is required is to replace all dates with the DD-MMM-YYYY format (i.e. with month displayed as text) or provide a localisation option.

Ambar D

Lucid community team

Hi @BlimeyBen, thank you for your comment and detailed feedback. I am thankful you took the time to share just how important this is to you and countless others, and the impact it has. I am truly sorry for the inconvenience here, and I can certainly understand how this may impact your work.

Your feedback here is very valuable to our product team who continues to review feedback within these threads.

J

jw009

I’ve been a long-time Lucid user and have appreciated the product for years. One ongoing issue, however, is that Lucid screens do not appear to default to the browser’s locale when displaying dates and times. Could you please address this as a priority? It would greatly improve the user experience.

Zuzia S

Lucid community team

@jw009 thank you so much for taking the time to share your experience here along with your feedback. I am very sorry for the inconvenience this is causing to your workflow. Although at this time we don’t have an update to share regarding this feature, the best way to indicate support for it to be implemented is to upvote this post.

S

Simon Reed

This requirement - to have Lucid products conform to the user’s PC’s locale settings - has been kicking around for many years and raised a number of times. One of the instances, raised EIGHT YEARS AGO is marked ‘SOLVED’, but it isn't. Another from 3 years ago, asking for ISO format dates as an option, has been marked ‘SOLVED’ but isn’t. It is a request raised many, many times but not actioned.

And marking the request as SOLVED when it isn’t does not help. It gives a false impression there is little demand for this, when in fact the people who would benefit are: the entire world other than the USA. Plus those in the USA who share work internationally.

That utterly illogical date format you have got hard-coded into Lucid products may be familiar to those in the USA, but it creates problems for everyone else.

This should not be an item for ‘future consideration’. IT IS A BUG. And ignoring it because you are a USA company is just showing contempt for everyone else in the world.

Ambar D

Lucid community team

Your feedback here is incredibly valuable @Simon Reed to highlight just how vital this feature is to you and many other users- thank you for your thoughtful and detailed comment here. I apologize for the frustration here.

We see and hear your feedback, and our product team continue to use comments just like yours in this section of the community as they research product enhancements.

M

m2468

Please allow the option of changing the date code to either dd/mm/yy or dd/mmm/yy.

I was going to use Lucid to manage my personal workflow but have now chosen another method as I know I will at some point read a date the wrong way round. (eg to me 6/7/26 is 6 Jul 26 but Lucid will provode 7/6/26 and I will think that means 7 Jun 26).

This date code bug is costing you business!

Ambar D

Lucid community team

Hi @m2468, thank you for letting us know just how important this is to you.

I certainly understand how it may impact your work, and I appreciate you taking the time to let us know what you’d like to see. Our product teams are regularly reviewing feedback from comments just like yours as they continue to research new product features and enhancements.

Create an account in the community

Log in to the community