-
Type:
Bug
-
Resolution: Not a bug
-
Priority:
High
-
Component/s: Work Item - Backend - Update
-
None
-
1
-
Severity 2 - Major
-
0
Hi everyone,
We have investigated this bug and found that it is working as expected.
The configuration "jira.date.picker.java.format" is to parse a string value to date before storing into the DB.
When the configuration is incorrect, the system will incorrectly read the value, which cause incorrect value in the DB.
This happens to any updates in Jira, not just JCMA.
When this occurs, please correct the format for "jira.date.picker.java.format" and re-try your operation.
Issue Summary
All date fields incorrectly store the month as January after DC2C migration using JCMA when jira.date.picker.java.format on target cloud is set wrongly as yyyy/mm/dd (lowercase m as minutes) rather than yyyy/MM/dd (uppercase M as months).
Steps to Reproduce
Pre-requisites
- Jira Data Center (source) has jira.date.picker.java.format from Jira system advanced settings correctly configured as yyyy/MM/dd (uppercase M as months).
- Jira Cloud (target) has the same setting incorrectly configured as yyyy/mm/dd (lowercase m as minutes).
Steps
- Create a custom field of type date, for example, "Delivery Date"
- Create multiple issues with custom field "Delivery Date" as 2026/07/08 (no values containing `01`)
- Set values for system fields such as "Due Date" as 2026/07/02 (no values containing `01`)
- Migrate issues where issues have "Delivery Date" custom field and "Due Date" (both of type date) using JCMA.
Tested using JCMA 1.17.1 - Observe same issue in Jira Cloud.
The values seem to have been changed during the import phase as they were in the correct format when exported.
Expected Results
Date values should remain the same as when exported.
Actual Results
All date fields incorrectly display the month as January.
Workaround
Currently there is no known workaround for this behaviour. A workaround will be added here when available.
