-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
10.4.0
-
7
-
Severity 3 - Minor
-
15
Issue Summary
Date and time values selected via the ProForma date picker are being incorrectly parsed when the form language differs from the Jira system default language. This leads to misinterpretation of the selected date — especially when day and month positions are ambiguous across locale formats (e.g., DD/MM vs. MM/DD).
Steps to Reproduce
- Install Jira DC and Proforma
- Set the Jira default language to US English
- Create a Proforma form like the below -
- Scenario 1 - Go to an issue, add the form, select the dates like 6th Mar 2025.
- Scenario 2 -Go to an issue, add the form, select the dates like 13th Mar 2025 (Dates higher than 12).
Expected Results
The dates get updated to 6th Mar 2025 in the form and in the Change Start date.
Actual Results
- Scenario 1 - The change start date gets updated to 6th Mar 2025 but the Form shows June 3rd 2025.
- Scenario 2 - When the date updated is higher than 12 (May 13 or higher), Form validates the date value with the month and displays "Invalid Date" in the field.
Workaround
Make sure to use the Form language the same as the default language in Jira. This will help with the new forms.
The old forms still render as 'Invalid date' even after changing the language settings (if the date chosen is greater than 12). There is no way to correct this at the moment.
- relates to
-
-
- Gathering Impact
-
- links to
[FORMDC-838] Date Picker Values in Jira Forms (ProForma) Are Misinterpreted Due to Locale Parsing Mismatch
| Support reference count | Original: 6 | New: 7 |
| UIS | Original: 6 | New: 15 |
| Support reference count | Original: 5 | New: 6 |
| UIS | Original: 5 | New: 6 |
| Support reference count | Original: 4 | New: 5 |
| UIS | Original: 4 | New: 5 |
| UIS | Original: 3 | New: 4 |
| Support reference count | Original: 3 | New: 4 |
| Description |
Original:
h3. Issue Summary
Date and time values selected via the ProForma date picker are being incorrectly parsed when the form language differs from the Jira system default language. This leads to misinterpretation of the selected date — especially when day and month positions are ambiguous across locale formats (e.g., DD/MM vs. MM/DD). h3. Steps to Reproduce * Install Jira DC and Proforma * Set the Jira default language to US English * Create a Proforma form like the below - !Screenshot 2025-04-08 at 6.39.20 PM.png|thumbnail! !Screenshot 2025-04-08 at 6.40.12 PM.png|thumbnail! * *Scenario 1* - Go to an issue, add the form, select the dates like 6th Mar 2025. * *Scenario 2* -Go to an issue, add the form, select the dates like 13th Mar 2025 (Dates higher than 12). h3. Expected Results The dates get updated to 6th Mar 2025 in the form and in the Change Start date. h3. Actual Results * *Scenario 1* - The change start date gets updated to 6th Mar 2025 but the Form shows June 3rd 2025. !Screenshot 2025-04-08 at 7.51.06 PM.png|thumbnail! * *Scenario 2* - When the date updated is higher than 12 (May 13 or higher), Form validates the date value with the month and displays "Invalid Date" in the field. !Screenshot 2025-05-02 at 5.36.46 PM.png|thumbnail! !Screenshot 2025-05-02 at 5.38.26 PM.png|thumbnail! h3. Workaround Make sure to use the Form language the same as the default language in Jira. Even after editing the languages, the old forms still render as 'Invalid date' if the date chosen is greater than 12. There is no way to correct this at the moment. |
New:
h3. Issue Summary
Date and time values selected via the ProForma date picker are being incorrectly parsed when the form language differs from the Jira system default language. This leads to misinterpretation of the selected date — especially when day and month positions are ambiguous across locale formats (e.g., DD/MM vs. MM/DD). h3. Steps to Reproduce * Install Jira DC and Proforma * Set the Jira default language to US English * Create a Proforma form like the below - !Screenshot 2025-04-08 at 6.39.20 PM.png|thumbnail! !Screenshot 2025-04-08 at 6.40.12 PM.png|thumbnail! * *Scenario 1* - Go to an issue, add the form, select the dates like 6th Mar 2025. * *Scenario 2* -Go to an issue, add the form, select the dates like 13th Mar 2025 (Dates higher than 12). h3. Expected Results The dates get updated to 6th Mar 2025 in the form and in the Change Start date. h3. Actual Results * *Scenario 1* - The change start date gets updated to 6th Mar 2025 but the Form shows June 3rd 2025. !Screenshot 2025-04-08 at 7.51.06 PM.png|thumbnail! * *Scenario 2* - When the date updated is higher than 12 (May 13 or higher), Form validates the date value with the month and displays "Invalid Date" in the field. !Screenshot 2025-05-02 at 5.36.46 PM.png|thumbnail! !Screenshot 2025-05-02 at 5.38.26 PM.png|thumbnail! h3. Workaround Make sure to use the Form language the same as the default language in Jira. This will help with the new forms. The old forms still render as 'Invalid date' even after changing the language settings (if the date chosen is greater than 12). There is no way to correct this at the moment. |
| Description |
Original:
h3. Issue Summary
Date and time values selected via the ProForma date picker are being incorrectly parsed when the form language differs from the Jira system default language. This leads to misinterpretation of the selected date — especially when day and month positions are ambiguous across locale formats (e.g., DD/MM vs. MM/DD). h3. Steps to Reproduce * Install Jira DC and Proforma * Set the Jira default language to US English * Create a Proforma form like the below - !Screenshot 2025-04-08 at 6.39.20 PM.png|thumbnail! !Screenshot 2025-04-08 at 6.40.12 PM.png|thumbnail! * *Scenario 1* - Go to an issue, add the form, select the dates like 6th Mar 2025. * *Scenario 2* -Go to an issue, add the form, select the dates like 13th Mar 2025 (Dates higher than 12). h3. Expected Results The dates get updated to 6th Mar 2025 in the form and in the Change Start date. h3. Actual Results * *Scenario 1* - The change start date gets updated to 6th Mar 2025 but the Form shows June 3rd 2025. !Screenshot 2025-04-08 at 7.51.06 PM.png|thumbnail! * *Scenario 2* - When the date updated is higher than 12 (May 13 or higher), Form validates the date value with the month and displays "Invalid Date" in the field. !Screenshot 2025-05-02 at 5.36.46 PM.png|thumbnail! !Screenshot 2025-05-02 at 5.38.26 PM.png|thumbnail! h3. Workaround Make sure to use the Form language the same as the default language in Jira. |
New:
h3. Issue Summary
Date and time values selected via the ProForma date picker are being incorrectly parsed when the form language differs from the Jira system default language. This leads to misinterpretation of the selected date — especially when day and month positions are ambiguous across locale formats (e.g., DD/MM vs. MM/DD). h3. Steps to Reproduce * Install Jira DC and Proforma * Set the Jira default language to US English * Create a Proforma form like the below - !Screenshot 2025-04-08 at 6.39.20 PM.png|thumbnail! !Screenshot 2025-04-08 at 6.40.12 PM.png|thumbnail! * *Scenario 1* - Go to an issue, add the form, select the dates like 6th Mar 2025. * *Scenario 2* -Go to an issue, add the form, select the dates like 13th Mar 2025 (Dates higher than 12). h3. Expected Results The dates get updated to 6th Mar 2025 in the form and in the Change Start date. h3. Actual Results * *Scenario 1* - The change start date gets updated to 6th Mar 2025 but the Form shows June 3rd 2025. !Screenshot 2025-04-08 at 7.51.06 PM.png|thumbnail! * *Scenario 2* - When the date updated is higher than 12 (May 13 or higher), Form validates the date value with the month and displays "Invalid Date" in the field. !Screenshot 2025-05-02 at 5.36.46 PM.png|thumbnail! !Screenshot 2025-05-02 at 5.38.26 PM.png|thumbnail! h3. Workaround Make sure to use the Form language the same as the default language in Jira. Even after editing the languages, the old forms still render as 'Invalid date' if the date chosen is greater than 12. There is no way to correct this at the moment. |