English (Canada) locale short date format is wrong in Classic UI

Products

• Clarity PPM On Premise
• Clarity PPM SaaS

Issue/Introduction

When using English (Canada) locale, found that short date in Clarity PPM in Classic is using wrong formats in some pages.

STEPS TO REPRODUCE:

Note this is just an example and date should be using yyyy-mm-dd everywhere where short date is used

1. Connect to Clarity Classic - Home - Account Settings
2. Set your user Locale to English (Canada) and Save
3. Log out, log back in
4. Go to Classic Timesheets, open a timesheet
5. Note in the drop down you can see the Time Periods

Expected Results: See the time periods in Canada short date locale, yyyy-mm-dd

Actual Results:The time periods are displayed in dd/mm/yy

Environment

All Supported Clarity Releases 

Cause

DE79432 / DE170370

Resolution

Reviewed for consideration to be added as user story: Not technically feasible due to impact

Workaround:

1. Update the properties.xml file for the app service to add the below JVM parameter:
   -Djava.locale.providers=CLDR,COMPAT,SPI
   Example:
       <applicationServerInstance id="app" serviceName="Clarity PPM App Server" rmiPort="23791" jvmParameters="-Xms512m -Xmx2048m -XX:-UseGCOverheadLimit -DforceMemorySettings=false -XX:MaxMetaspaceSize=512m -Djava.locale.providers=CLDR,COMPAT,SPI" maxThreads="1000" programParameters="" distributed="false" runJobScheduler="false" useSSO="false" maxConcurrentJobs="10" runProcessEngine="false" messageTimeToLive="120" messageReceiverInterval="5" exceptionRunInterval="normal" serviceType="app" pushServiceLivenessInterval="180" statusMonitorInterval="300">
         <war context="pm" name="ppm-ux" enable="true"/>
   
   
2. Restart all services

If you still see error in Classic Timesheets such as below:

Timesheet filter is no longer working. 

1. Go to Classic Timesheets
2. Filter on Custom Range - enter a date in the calendar

Click Filter - error message "Incorrect date format"

Recommendation is to switch to using MUX Timesheets - unfortunately the impact of the change would be too great to update this