Issue Summary

When using the Jira Align console with the browser set to use the Australia date format of DD/MM/YYYY (and not the US format of MM/DD/YYYY), if a user creates a new feature and sets the the Start / Initiation and/or Target Completion Dates before the first save, then on clicking Save, a US date format is applied and two invalid results can be seen:

• If the numeric value entered for DD (in the DD/MM/YYYY format) is greater than 12, then the date will show as blank (because the US date format of MM/DD/YYYY does not expect a number greater than 12 to be present in the MM field)
• If the numeric value entered for DD (in the DD/MM/YYYY format) is 12 or less, then the date after the save will show the date and month swapped over, for instance if you entered 09/07/2025 you will see 07/09/2025

These fields work correctly for an existing Feature.

Steps to Reproduce

1. Set browser to locale/language other than US, for example, English (Australia)
2. Add a new Feature with Start / Initiation and Target Completion Dates fields filled with dates higher than 12, for example 13 Oct
3. Click Save
4. Observe the fields are empty
5. Observe the Audit log contains the dates
6. Filling dates with day value 1-12 sets the dates, but swaps the day and month values

Expected Results

The date should save correctly no matter what date format is being used in the browser settings or if the action is either: create a new feature or edit an existing feature.

Actual Results

The date is not saved correctly when using a browser set to an English (Australia) date format, when creating a new feature but is saved correctly when editing an existing feature.

Workaround

• Save the Feature once before setting the dates
• Set the browser to use English (United States) language