-
Bug
-
Resolution: Fixed
-
Low (View bug fix roadmap)
-
6.3.12, 6.3.15
-
6.03
-
NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.
Summary
STRM-2272 might cause a timeout with a message saying "The activity source for 'JIRA' was slow to respond and isn't included." and "No activity was found" where the data should be when trying to view Activity Stream gadgets. This issue tracks the upgrade of JIRA to use a more recent version of Activity Streams (5.4.13) in which the issue was fixed.
Steps to Reproduce
This issue can be replicated in environments where issues have very long histories and many records are returned.
Expected Results
The Activity Stream is expected to show the stream of activities.
Actual Results
The Activity Stream shows an error reporting no activities, or the slow to respond message.
Notes
For more information, please see: STRM-2272 and JIRA Activity Stream returns One or more activity sources were slow to respond and are not included.
- relates to
-
JRASERVER-37905 Activity stream in the user profile times out easily on larger instances
-
- Closed
-
-
JRACLOUD-41629 Activity Stream can timeout for issues with very long histories
-
- Closed
-
-
FUSE-2088 Failed to load
- is related to
-
JSP-213769 You do not have permission to view this issue
-
STRM-2265 If an Issue has many change items it will time out
- Done
-
STRM-2272 Loading...
https://support.atlassian.com/servicedesk/customer/portal/23/JST-138965
Thanks.