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

JIRA Submits no form data after 5 minutes - Actions such as CreateIssue will then failed with a session expiry

      NOTE: The description for this bug is old. See Brads last 2 comments for the problem and potential solutions.

      There is a bug in FireFox 3.6 that causes it to POST zero parameters to the server.

      This tends to occur after say a 5 minutes time frame after say starting an issue and pressing submit.

      https://bugzilla.mozilla.org/show_bug.cgi?id=547239

      The bug report mentions that it has been fixed but at the time of this post, a new version of FireFox is not available.

      Our recommendation is to roll back to FireFox 3.5 or move up to FireFox 3.6.1 when it becomes available.

      MORE NOTES :

      Our QA staff have discovered the following

      This bug affects Windows/Linux(Ubuntu) when user has selected "Auto Detect proxy setting for network". If the option is "no proxy", its working fine without any issues.Tested with WinXp and Win Vista.

      Create Issue operation is working fine on Mac X.6 with FF 3.6 with both proxy set to no/Auto.

        1. 2016-09-04_203108.png
          2016-09-04_203108.png
          20 kB
        2. FireFox7.0.1.jpg
          FireFox7.0.1.jpg
          77 kB
        3. image-2021-07-15-18-45-24-675.png
          image-2021-07-15-18-45-24-675.png
          337 kB
        4. Safari_5.1.2.png
          Safari_5.1.2.png
          64 kB
        5. Screenshot.png
          Screenshot.png
          20 kB
        6. screenshot-1.jpg
          screenshot-1.jpg
          227 kB

            [JRASERVER-20696] JIRA Submits no form data after 5 minutes - Actions such as CreateIssue will then failed with a session expiry

            Ani Popova added a comment - - edited

            I am getting this issue too. Is there a workaround? 

            The issue happens mostly when I try to publish a Workflow Scheme that removes a workflow (because there are no more issues types associated with it). 

            My workaround was to do it in two steps: first make sure there is at least one issue type remaining in the workflow that I want to remove, and then do the same but just remove that last issue type remaining. It worked, but I wish this bug was fixed. 

            Ani Popova added a comment - - edited I am getting this issue too. Is there a workaround?  The issue happens mostly when I try to publish a Workflow Scheme that removes a workflow (because there are no more issues types associated with it).  My workaround was to do it in two steps: first make sure there is at least one issue type remaining in the workflow that I want to remove, and then do the same but just remove that last issue type remaining. It worked, but I wish this bug was fixed. 

            Received this error while doing bulk update on a Jira Cloud instance using chrome browser

            Jessica Wolfe (Inactive) added a comment - - edited Received this error while doing bulk update on a Jira Cloud instance using chrome browser

            I WANT TO MAKE IT CLEAR THIS IS NOT A BLOCKER FOR ME AT THE MOMENT.

            I am not able to select 'Contact an Administrator' from the Board Settings screen to access simplified workflow. I am using Chrome Browser Version 87.0.4280.88 (Official Build) (64-bit) at the moment, and my browser is telling me that I am up to date. 

            I feel this is a nuisance, but I am able to contact my system administrator through another medium. 

             

            Deleted Account (Inactive) added a comment - I WANT TO MAKE IT CLEAR THIS IS NOT A BLOCKER FOR ME AT THE MOMENT. I am not able to select 'Contact an Administrator' from the Board Settings screen to access simplified workflow. I am using Chrome Browser Version 87.0.4280.88 (Official Build) (64-bit) at the moment, and my browser is telling me that I am up to date.  I feel this is a nuisance, but I am able to contact my system administrator through another medium.   

            We have same issue but juste in 1 workflow scheme. 
            I have remove all data in my browser, but nothing to do ! It does not work ! 

            I have try to disable browser extension, but no change ! 

            I'm on cloud version on my side.

             

            Geoffrey CONTE added a comment - We have same issue but juste in 1 workflow scheme.  I have remove all data in my browser, but nothing to do ! It does not work !  I have try to disable browser extension, but no change !  I'm on cloud version on my side.  

            Same as the above. Seeing this error when trying to publish a new workflow. 

            Sage Ashique added a comment - Same as the above. Seeing this error when trying to publish a new workflow. 

            Issue reproduced when publishing a new workflow that has no issues that are associated with it.

            Nicolas Revill added a comment - Issue reproduced when publishing a new workflow that has no issues that are associated with it.

            knox_ner added a comment -

            I am also seeing the same issue when editing a workflow scheme on Jira Cloud.

            knox_ner added a comment - I am also seeing the same issue when editing a workflow scheme on Jira Cloud.

            ob added a comment -

            Found also this: https://confluence.atlassian.com/jirakb/changing-workflow-scheme-results-in-xsrf-token-error-695111066.html
            But what can users do who have the Cloud version of Jira?

            ob added a comment - Found also this: https://confluence.atlassian.com/jirakb/changing-workflow-scheme-results-in-xsrf-token-error-695111066.html But what can users do who have the Cloud version of Jira?

            Yes see this issue on edit workflow scheme

            Mark Crocker added a comment - Yes see this issue on edit workflow scheme

              Unassigned Unassigned
              bbaker ɹǝʞɐq pɐɹq
              Affected customers:
              10 This affects my team
              Watchers:
              59 Start watching this issue

                Created:
                Updated:
                Resolved: