The date format is fixed to mm/dd/yyyy, could this please be selectable based on your region - for example we use dd/mm/yyyy
As an update, since we’ve still been seeing issues around date formatting, so we’re pursuing another fix that should help: If you’re using Planner within Teams, we will default to using the same language/local as Teams.
If you’re seeing this issue persist outside of Teams and your language/locale is set properly for your Office account, please let us know in the comments below!
The Planner Team
we use dd/MMM/yy. We look forward to getting this implemented.
Ruth Jennaway commented
Why does Planner not follow the personal regional settings of Office365? Or even the tenancy Data centre region?
I am in the UK and a number of my clients have this issue.
Very off-putting for ordinary users just starting out with Planner.
Such a great tool - but only designed for American customers?
Jóhannes Jónsson commented
In Teams language settings I have selected Icelandic to determine date and time format that should be DD.MM.YYYY but the date and time format is still a US format MM.DD.YYYY
And there is no way to change the language settings in planner (!!!)
Come on, fix this. It´s the year 2020
anything is better than the US centric format. I work in the UK and communicate internationally, at the very least MS should adopt an ISO format such as yyyy-mm-dd if the logical ascending order of dd-mm-yyyy is too confusing
Not working in teams, when teams locale is set to UK, not working external either
Still seeing issues from Planner online when plan is not linked to Teams
Absolute nonsense. Using Planner via Office 365, not embedded in Teams. The date format here in Australia is wrong - this renders the product worse than useless as it is providing incorrect information.
E Dagher commented
Seriously Microsoft... a project and task planning tool that doesn't allow you to use dates in your native region format? Not everyone lives in the US.
Although I'm glad the date has been resolved if you open Planner in Teams, the full standalone program needs to be updated for differing date formats as a lot of my production of plans is done in this environment.
Adding in my support for this as there are over 5,258 Million people using Day/Month/Year format not Month/Day/Year
A planner that can't get the date setting right? Come on Microsoft - what are your priorities?
Rae Jobst commented
I want to add my support to this request... as others have said, it is annoying as it seems like you should already be able to do this and so you hunt around to try to find out where to change it. Another comment mentions changing the URL - this post provides more detail on that workaround: https://www.adamfowlerit.com/2018/07/how-to-change-the-microsoft-planner-date-format/
Have attempted all the work arounds without success. At the moment with a small number of people using the planner via teams it is OK and manageable but will not halt further deployment until dates can be correctly displayed for the region a person is working in.
Using MS Teams and the date format in Planner is defaulted to US. Not yet running on Windows 10 but all my system settings are UK region/date/language.
Virginia LM commented
we've just started using Planner within Teams. would be good to have flexibility to choose dd/mm/yyyy
Jesty Karl Salvatierra commented
workaround is change the bit of "en-US" to "en-AU" or "en-GB" or whatever time format, but then again, keen to get a permanent fix for this please product team.
Peter Sv commented
From what I can see, this i still not fixed and there's no way to work around it. At least I can now stop searching for what I thought I'd overlooked. This is such a silly problem to have. Crazy and annoying
David Cooper commented
I couldn't wait any longer and we have moved to another product. Its really disappointing that no one is looking after the ecosystem of office365 rather the product teams seem to just develop by themselves and the app launcher has no consistency between products. Project online was just rolled out and it does exactly the same thing. It doesn't even have the AU locale correct.
We will not be adopting Planner in my (Australian) organsiation on the basis of this issue alone.
This may seem a small issue to Microsoft HQ is the US but it's enough to put a lot of UK users off of using Oklanner. Which is a shame, as it is otherwise a good product