-
Bug
-
Resolution: Unresolved
-
Low (View bug fix roadmap)
-
None
-
9.7.0, 9.12.0, 9.7.2, 10.0.0, 9.12.11
-
9.07
-
2
-
Severity 3 - Minor
-
2
-
Issue Summary
When setting the End Date for a Release in a plan and saving the change to Jira, this will set the date by 1 day later when on MySQL 8
Setting the End Date via Project -> Releases in Jira itself is not affected
Setting the Start Date for the Release is not affected
Doing the same operation with PostgreSQL works as expected.
This starts with Jira Version 9.7, so is possibly related to the fix for https://jira.atlassian.com/browse/JRASERVER-41646
This is reproducible on Data Center: yes
Steps to Reproduce
- Set up Jira with MySQL 8 as database
- Create a SCRUM (or KANBAN) project with a release, and issues
- Create a plan using the project board as issue source
- Go to Plan -> Releases
- select the ... -> Edit for one of the releases and set the end date
- Go to "Review Changes" and save the changes to Jira
- Refresh the page and check the saved release end date
Expected Results
End date is the same date as entered
Actual Results
End date has shifted by one day
NOTE:
For example, setting the End Date to 14 September 2024 will show in
- MySQL : 2024-09-15 00:00:00
- Postgres: 2024-09-14 23:59:59.999 +0000
Workaround
Set the End Date for a Release using the Project -> Releases page
- links to
- mentioned in
-
Page Failed to load
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|