-
Bug
-
Resolution: Cannot Reproduce
-
Low
-
2
-
Severity 3 - Minor
-
Issue Summary
When creating a new release version directly fro the Kanban board the current date is automatically populated for the date of the release of the version. However, after committing the release if you review this in the list of released version on the releases page the release date is the day prior to the auto populated one from the Kanban board.
Steps to Reproduce
- Create a Kanban project and board.
- Create an issue.
- Progress this issue to a done status.
- Click the release button on the Kanban board.
- Select New version.
- Enter a version name in the pop-up dialogue but leave the populated date (which should be the current date).
- Click the Release button.
- Now view the list of released versions from the projects releases page.
Expected Results
The release date for the version just release should be the same pre-populated date, that being the current day.
Actual Results
The release date is set to the day prior to the date specified when creating the release from the Kanban board
Workaround
- Create the release in the project release page.
- Assign the release to the Fix version field of the issues to be incorporated into this release.
- Progress the issue to the done status.
- Click the release button on the Kanban board and select the existing release.
- Populate a release date a click the release button.
- Review the release in the projects release page
- is related to
-
-
- Closed
-
- relates to
-
-
- Closed
-
[JRACLOUD-87045] Incorrect date in the release page for new releases created directly from Kanban board
I couldn't replicate this bug. I've tried to use different timezones: +10, -10
I believe this is fixed somehow since this bug has been raised in 2019. Can anyone replicate this bug today?
Hi all,
Thank you for raising this bug and bringing it to our attention.
Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved.
To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users.
No change nor update as of 11 June 2020. Below what I got by email with Atlassian last month and the month before.
Thread: JST-521948 Still affected by JRACLOUD-67487
Update on 28 April 2020:
I just wanted to update you, I have spoken directly with the developer on:
•
JRACLOUD-67487: Versions showing start date and release date 1 day earlierHe informed that this bug has been progressed by his team as far as can be, the last piece of work is indeed the Kanban board as detailed here:
•
JSWCLOUD-18526: Incorrect date in the release page for new releases created directly from Kanban boardThis is why no update has been placed on this bug for a while. Now I have raised a case internally to chase the progress of
JSWCLOUD-18526so please bear with me while I chase this and try and get an update for you.
Update on 18 May 2020:
I just wanted to drop a courtesy update to let you know I am in talks with engineering about updates on https://jira.atlassian.com/browse/JSWCLOUD-18526 [...] I will let you know as soon as I have more info.
This problem had disappeared all winter (uk winter time = UTC), and it re-appeared at the end of March with the switch to summer time (British Summer Time BST = UTC+1). As mentioned in previous posts.
This ticket was marked as “short term backlog” 5 months ago and no change since.
The linked ticket https://jira.atlassian.com/browse/JRACLOUD-67487 was marked “In progress” on 26 June 2018 and not updated since.
Ironically, it takes so long for this issue to be fixed that we can go through several winter and summer time changes to verify.
I am closing this as unreproducible for now. I believe it may have already been fixed sometime in the last three years. If anyone is still able to reproduce this let me know on the ticket.