Details
-
Bug
-
Resolution: Fixed
-
Low
-
6.0.2
-
6
-
Description
When using the Date Time custom field type, the property to disable relative dates and times is not respected. Screenshot of repro, and correctly picked up property from the System Info page to confirm.
Steps to repro:
I just took a clean instance, added a single custom field with a date time type. This field applied to every single project and screen. The instance had the property set in the jira-config.properties file, and was confirmed to be set during runtime in the System Information page. Then I created multiple issues. These issues all had the test custom field set on them. The values set were between 48 hours old, and 48 hours in the future. Some values were within hours of now, others within minutes. Everything within a short period of time showed up with relative time instead of absolute.
Attachments
Issue Links
- is duplicated by
-
JRASERVER-33876 Hours and minutes do not respect jira.lf.date.relativize = false
- Closed
- relates to
-
JRASERVER-33747 Datetime custom fields do not render the same way as system datetime fields
- Closed