Details
-
Bug
-
Status: Done
-
High
-
Resolution: Fixed
-
5.4.12
-
None
-
None
-
Sprint 40, Sprint 41, Sprint 42
-
1.1
Description
The function 'dateCompare' produces random results when under stress. The error is intermittent and believe it depends on the load of the server. This can be reproduced in Navigator or in dashboards when used in gadgets' filters. Find attached a pdf with steps to reproduce that was provided by one of our users.
If your instance is under heavy load, and you make a large query 10 times in a row, the return of that query will be different each time. An example of the query could could be something like this:
issueFunction in dateCompare("", "resolutionDate < dueDate + 1d") AND issueFunction in dateCompare("", "resolutionDate < dueDate + 2d") AND issueFunction in dateCompare("", "resolutionDate < dueDate + 3d") AND issueFunction in dateCompare("", "resolutionDate < dueDate + 4d") OR issueFunction in dateCompare("", "resolutionDate < dueDate + 1w") AND issueFunction in dateCompare("", "resolutionDate < dueDate + 2w") AND issueFunction in dateCompare("", "resolutionDate < dueDate + 3w") AND issueFunction in dateCompare("", "resolutionDate < dueDate + 4w")
There are concise steps to reproduce this in the pdf. This was reproduced in an instance with over 50K issues.
Attachments
Issue Links
- causes
-
SRJIRA-467 Time Since Gadget configured with a filter using dateCompare throws error
-
- Done
-
- is related to
-
SRJIRA-2446 Nested filters with dateCompare queries throw exceptions
-
- Done
-