We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-41629

Activity Stream can timeout for issues with very long histories

      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.

        1. screenshot-1.png
          screenshot-1.png
          61 kB
        2. screenshot-2.png
          screenshot-2.png
          95 kB

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
            Uploaded image for project: 'Jira Data Center'
            1. Jira Data Center
            2. JRASERVER-41629

            Activity Stream can timeout for issues with very long histories

                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.

                  1. screenshot-1.png
                    screenshot-1.png
                    61 kB
                  2. screenshot-2.png
                    screenshot-2.png
                    95 kB

                        ohernandez@atlassian.com Oswaldo Hernandez (Inactive)
                        malmeida Marcus Silveira
                        Votes:
                        31 Vote for this issue
                        Watchers:
                        61 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                            ohernandez@atlassian.com Oswaldo Hernandez (Inactive)
                            malmeida Marcus Silveira
                            Affected customers:
                            31 This affects my team
                            Watchers:
                            61 Start watching this issue

                              Created:
                              Updated:
                              Resolved: