• 0
    • 15
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.

      Problem Definition

      As we know the activity stream in user profile are not possible to be customizable to retrieve the information needed, it is an known case that the activity stream in user profile would possibly
      time out after 10 seconds(the default timeout) especially when the JIRA instance integrated with many other application(eg. Confluence).

      Suggested Solution

      As there's no plan for activity stream being configurable in other parts of JIRA as specified here, add an option in General Configuration for administrator to configure the default timeout for activity stream to be user specified, so it could be longer than 10 seconds.

          Form Name

            [JRACLOUD-32255] Configuration for default timeout in activity stream

            Atlassian Update - January 2024

            Hi everyone,

            Thank you for bringing this suggestion to our attention.

            As explained in our new features policy, there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritize and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order.

            Unfortunately, as a result of inactivity (no votes or comments for an extended period of time), this suggestion didn’t make it to the roadmap and we are closing it.

            While this issue has been closed, our Product Managers continue to look at requests in https://jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket.

            Thank you again for providing valuable feedback to our team!

            Anusha Rutnam added a comment - Atlassian Update - January 2024 Hi everyone, Thank you for bringing this suggestion to our attention. As explained in our new features policy , there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritize and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order. Unfortunately, as a result of inactivity (no votes or comments for an extended period of time), this suggestion didn’t make it to the roadmap and we are closing it. While this issue has been closed, our Product Managers continue to look at requests in https://jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket. Thank you again for providing valuable feedback to our team!

            We moved form Jira Server to Cloud and now our users got this exact problem.

            Please fix this in Cloud.

            Stefan Höltker added a comment - We moved form Jira Server to Cloud and now our users got this exact problem. Please fix this in Cloud.

            Dave C added a comment -

            Dave C added a comment - This is a dupe of https://ecosystem.atlassian.net/browse/STRM-2140

              Unassigned Unassigned
              yen@atlassian.com TeckEn (Inactive)
              Votes:
              8 Vote for this issue
              Watchers:
              15 Start watching this issue

                Created:
                Updated:
                Resolved: