Details
-
Bug
-
Resolution: Unresolved
-
High
-
None
-
9.4.0, 9.5.0, 9.6.0, 9.7.0, 9.8.0, 9.9.0, 9.10.0, 9.9.1, 9.11.0, 9.4.9, 9.12.0, 9.4.10, 9.4.15, 9.12.1, 9.13.0, 9.14.0, 9.12.4, 9.4.18
-
None
-
9.04
-
8
-
Severity 2 - Major
-
43
-
Description
Issue Summary
After upgrade to a version 9.4.x or above, it is noticed that email subscription results for a filter do not get latest results from the filter. The results are either older or missing the latest issue that was updated, to be part of the filter. Therefore users get emails with inaccurate results. This problem persists even after a full re-index of the instance.
Steps to Reproduce
- Create a issue that will fall under the saved filter by moving it to 'requiring approval' status results such as
project in (SCRUM,KAN) and status in ('Requiring Approval', 'In progress', 'Escalated') and Component not in ('Loss')
- Running the above JQL in the search window, would show the new issue that was moved to the 'Requiring Approval' status.
- Force a subscription run for the above filter right after. The mail received would not contain the recent most issue.
- Even subsequent runs of the scheduled subscription for the same filter, does not contain the recent issue. They are eventually received in the subscription results several hours later.
Expected Results
The the email subscription results for a filter should always match the results for the same filter when run from the UI.
Actual Results
The emails subscription results for the filter are stale. They provide proper results only after several hours later.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available