Due date field shows different value than what user selected on transition screen
Platform Notice: Cloud - This article applies to Atlassian products on the cloud platform.
Summary
Adding a value to the Due date field on a transition screen, appears incorrectly on the issue view. For example, when the date 17/May/2024 is selected from the calendar, the Due date field on the transition screen, is updated to May 15, 24 on the issue view.
Environment
Jira Cloud
Cause
There is a mismatch in the jira.date.picker.java.format
and jira.date.picker.javascript.format
properties.
Diagnosis
To understand where these properties reside on the cloud site,
- Navigate to the Settings icon → General configuration page and click Advanced Settings or
- Directly open this link: https://<yoursitename>.atlassian.net/secure/admin/AdvancedApplicationProperties.jspa
Solution
To correct the properties,
- Go to Settings icon → General configuration page and click Advanced Settings or
- Directly open this link: https://<yoursitename>.atlassian.net/secure/admin/AdvancedApplicationProperties.jspa
As mentioned indirectly in Changing the Due Date Input Format, ensure that the values of jira.date.picker.java.format
property and that of the jira.date.picker.javascript.format
property match as per the following table:
Value of the jira.date.picker.java.format property | Value of the property | |
---|---|---|
1. | dd | %d |
2. | MM | %m |
3. | yyyy | %Y |
4. | MMM | %b |
5. | d | %e |
6. | yy | %y |
7. | MM | %m |
Apply the same to the values of jira.date.time.picker.java.format
and jira.date.time.picker.javascript.format
:
Value of the jira.date.time.picker.java.format property | Value of the property | |
---|---|---|
8. | HH | %H |
9. | mm | %M |
10. | h:mm a | %l:%M %p |
11. | hh:mm a | %I:%M %p |
Contact Atlassian support if you have any questions.