Date format should be customizable and match user's location in timelines and across Lucid

Please edit the typo in the title, thanks

Hi ​@CraigC, thank you for your feedback! I can certainly see how this would be beneficial to other countries with different date and time formats, thank you for sharing. The product development team regularly reviews feedback within this space as they research new features and product enhancements. 

 We encourage anyone else who’s interested in this to upvote this post and share any additional details about your use case or what you’d like to see in this experience. For more information about how we manage feedback in this community, please take a look at this post:

It’s not limited to Jira cards. It’s everywhere in Lucid. Everything must be consistent and in the user’s locale. For Jira specifically, the dates are coming through from Jira in ISO standard format, so you are taking a decision in your business logic layer to translate the ISO format into US specific format. That’s the point where you should be picking up the settings in the user’s browser and using that instead, however this comment is not restricted to Jira, it’s everywhere dates are used.

Digital Equipment Co Ltd and Microsoft both US based companies largely solved this problem in the 1980s.

Hi ​@CraigC, sorry for any misunderstanding and thank you for clarifying with those details. We highly value your feedback and are committed to continually improving our products. I’ve updated the title of this post to reflect your comment here. 

It’s everywhere the US date format is used. All date formats must be in the user’s locale as swapping between date formats such is 10/11/2025 and 11/10/2025 with knowing which is which is a recipie for confusion. It’s like deciding to drive on the right or the left some of the time. It does not work.

How this is not a basic feature is beyond me. To deliberately force US format for dates instead of using regional settings is just crazy. Only one country in the world uses the MDY format...

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. 

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.

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.

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.

​@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.