-
Bug
-
Resolution: Timed out
-
Medium
-
72
-
Severity 3 - Minor
-
1
-
Summary
CSAT report does not show information.
Steps to Reproduce
Answer the satisfaction survey after a ticket is closed, it's not clear what triggers the double information on the database yet.
Expected Results
Only one satisfaction information should be logged on the database.
Actual Results
Somehow two entries were found for satisfaction and satisfaction dates custom fields in the database with a difference of two milliseconds related to the same issue, which got the satisfaction report stuck.
e.g.
DVS-1070,Satisfaction date,2017-10-10T19:19:07.915Z,2017-10-10T19:19:07.940866Z,2017-10-10T19:19:07.940866Z
DVS-1070,Satisfaction date,2017-10-10T19:19:07.931Z,2017-10-10T19:19:07.956909Z,2017-10-10T19:19:07.956909Z
Notes
It happened twice with the same user when answering the satisfaction survey.
When running the JQL behind the satisfaction report and the defective issue is on the list, the error 500 returns.
When running without ORDER BY Satisfaction date DESC the error does not appear.
Workaround
Contact support.
- is blocked by
-
JRACLOUD-71739 JQL order by on jira date custom field with duplicate values cause 500 error
-
- Closed
-
- derives
-
ACTIVE-1609 Loading...
- is caused by
-
ACTIVE-3165 Loading...
-
FSN-62 Loading...
-
FSN-116 Loading...