-
Bug
-
Resolution: Fixed
-
Low
-
3.12.2, 3.13.0, 3.14.0, 3.14.2, 3.15.1
-
8
-
Severity 3 - Minor
-
4
-
Problem definition
If the date time picker custom field is empty, the current date and time will be shown as the value in the portal request view and the value is real-time.
Steps to reproduce the issue
- Create a custom field of date time picker type and add it to the issue type screen.
- Add the field to the request form but leave it optional.
- Create the request without selecting a value on the date time custom field.
Expected result
The custom field will not appear on the created request because it has no value.
Actual result
The custom field appears on the created request with the current date and time (and keep updating) as the value.
- On the Agent's view of the issue, the custom field does not appear because it has no value in the issue.
Workaround
Configure a default value for the custom field e.g. the current date and time option to reduce the occurrence of this bug
- is cloned by
-
JSMDC-2821 You do not have permission to view this issue
- mentioned in
-
Page Failed to load
[JSDSERVER-5896] If the date time picker custom field is empty, it will always display the current date and time on the request view
Deleted Account (Inactive)
added a comment - Fix for this bug is crucial! There is no usable workaround and it impacts our customers!!
Please do something about it.
Deleted Account (Inactive)
added a comment - Fix for this bug is crucial! There is no usable workaround and it impacts our customers!!
Please do something about it. Problem still exists also in the newest version of Service Desk 3.15.1.
Suggested workaround with predefined values cannot be implemented, because that fields are used to calculate SLA and raports.
Those DataTime fields have high role in process, because related workflows are based on filled dates.
Atlassian please fix that bug as quick as You can.
This is very urgent for my Company because of process dependencies and we cannot move forward with production deployments.
Christian Brien
added a comment - Message to Atlassian Developers :
Please note that, unfortunately, the temporary workaround suggested cannot be implemented in every scenario.
In one of our use cases, we cannot set those date-time fields with predefined values because they sometimes need to remain empty, depending on other choices reporters make on the form via the Service Desk portal.
Those date-time fields should sometimes remain totally empty, and hidden, not being pre-populated.
If we pre-populate them, it defeats the purpose, and will at times cause user confusion if they appear with a value instead of remaining empty.
We will continue to wait for a fix.
Christian Brien
added a comment - Message to Atlassian Developers :
Please note that, unfortunately, the temporary workaround suggested cannot be implemented in every scenario.
In one of our use cases, we cannot set those date-time fields with predefined values because they sometimes need to remain empty, depending on other choices reporters make on the form via the Service Desk portal.
Those date-time fields should sometimes remain totally empty, and hidden, not being pre-populated.
If we pre-populate them, it defeats the purpose, and will at times cause user confusion if they appear with a value instead of remaining empty.
We will continue to wait for a fix.
Can this issue be elevated? Our users are confused seeing the extra dates.