Merged
Conversation
tarekio
approved these changes
Aug 28, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Jira Issue
Description
The date field format was updated to DD/MM/YYYY to be consistent across the database (I think). However, when entering dates manually, the system still requires the MM/DD/YYYY format.
This causes incorrect interpretations of entered dates. For example:
If the DA enters 3/5/2025 (expecting 3rd May 2025), the system interprets it as 5th March 2025 and displays it as 5/3/2025.
If the DA enters a date that cannot be flipped, e.g. 20/5/2025, the system rejects it, since it cannot interpret 20 as a month.
Display format: DD/MM/YYYY
Manual input requirement: MM/DD/YYYY
Checklist
API Changes (if applicable)
Additional Notes
[Any other relevant information]