Welcome to Atlassian
To report a bug or suggest a feature please raise an issue in our public
Customize this welcome note.
Not a member? Signup for an account.
Forgot your password?
You are running
Crucible 4.2.1 with
If you are experiencing any issues, please contact your administrator. You may also want to
browse the documentation
support forums. Still stuck? You can start a
ticket at support.atlassian.com or raise a bug or
feature request at jira.atlassian.com.
Customize the support message.
I didn't find any place where we are comparing dates from the database to the current timestamp, but I replaced hardcoded zone with SQL function NOW().
We decided on standup that the current version is correct
could check how do we handle such cases in other parts of the system?
Nikodem Graczewski Klaudia Pałkowska Should we treat those changes are breaking changes?
Please, add changelog.
Should we add changelog for this?
Because it's better in my opinion and it was the original idea from what I remember.
I thought that our database stores ZonedDateTimes in UTC.
but still why we are renaming the field?
Yes, I've adjusted UI.
why we use hardcoded zone here?
why we are not using setter annotation for the field? I don't see anything special here
why the field has been renamed? Does UI handle new field name?
Got a suggestion or an issue?
Discuss it on Atlassian Answers or
visit Atlassian Support for other options.