Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-38394

Issue Collector displays 'Oops! Something went wrong...' if the user's session times out

    XMLWordPrintable

Details

    • 5.02
    • 6
    • Severity 3 - Minor
    • 1
    • Hide
      Atlassian Update – 31-10-2018

      Hi everyone,

      We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future, i.e. in next 6 months.

      Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Jira team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details.

      We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication.

      Atlassian will keep the issue open and continue to watch this issue for the further updates.

      Thank you,
      Ignat Alexeyenko
      Jira Bugmaster

      Show
      Atlassian Update – 31-10-2018 Hi everyone, We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future, i.e. in next 6 months. Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Jira team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details. We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication. Atlassian will keep the issue open and continue to watch this issue for the further updates. Thank you, Ignat Alexeyenko Jira Bugmaster

    Description

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

      Summary

      When users attempt to submit information through an issue collector, it can randomly display 'Oops! Something went wrong...'. There is no specific information about what that error is.

      Steps to Reproduce

      1. Setup an issue collector.
      2. Set the session timeout to 1 minute as per Changing the default session timeout.
      3. Open up the issue collector.
      4. Wait for the user session to timeout.
      5. Attempt to submit the form.

      Expected Results

      The collector displays a specific error about how the user's session has timed out.

      Actual Results

      The 'Oops! Something went wrong...' error appears.

      Workaround

      Increase the session timeout as per Changing the default session timeout.

      Notes

      There are at least two ways to trigger this problem. Let's imagine the session timeout is 10 minutes.

      • Scenario A
        • T=0m: The user opens the feedback collector
        • T=0m: A new anonymous session is created (i.e. the user receives a JSESSIONID)
        • T=11m: The user submits the form. The JSESSIONID has timed out and it triggers the 401 response.
      • Scenario B
        • T=0m: The user opens the feedback collector and receives an anonymous session (for example, JSESSIONID=123)
        • T=1m: The user submits the feedback. Everything is ok at this point. The JSESSIONID=123 is still valid
        • T=9m: The user opens the feedback collector again. As they still have a valid JSESSIONID, no new session is created
        • T=11m: They submit the feedback using JSESSIONID=123. This session is now timed out, so they receive the 401.

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. JRACLOUD-38394 Issue Collector displays 'Oops! Something went wrong...' if the user's session times out

          • Low - Low priority issues
          • Closed
          derives

          DALEK-107 Loading...

          Activity

            People

              Unassigned Unassigned
              dcurrie@atlassian.com Dave C
              Votes:
              12 Vote for this issue
              Watchers:
              11 Start watching this issue

              Dates

                Created:
                Updated: