No components marked as affected
Write-up published
Resolved
Root Cause
A production update was made on the date/due date fields, however, due to the Locale/Timezone from a few users being null it caused this issue.
Resolution
We reverted the production application to the latest working version
Action Plan
We will apply some changes when a user is created and the timezone/locale is fulfilled in order to avoid date/due date issues in the future.
Resolved
This incident has been resolved.
Monitoring
A fix has been implemented and we are monitoring the results.
Identified
The issue has been identified and a fix is being implemented.