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

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. 

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.

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

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

Similar issue when publishing a edited workflow scheme. It gets stuck on step 1 of 2.

Same here, issue occurs during publishing a new workflow version.

The same problem as John Herndon described  

Happening to us when we try and publish a workflow. Was working fine most of the day and yesterday something stopped working. Tried latest versions of Chrome, Firefox, and Brave. Including Incognito.. flushed cache. Logout/login. restarted computer. tried second computer. Nothing works. Put in a support ticket. Still waiting for a response. Jira Cloud instance. I'm just adding this here because the error message links to this ancient bug, but the issue still persists.

+1 With Brave Browser

Getting this error as well. How is this marked closed?

I'm getting this error in chrome while using Bulk Edit in Jira Cloud.

im getting this error on all browsers for trying to clear the default for resolution field.

I'm in chrome and getting this issue when Bulk Edit changing priority, not on createissue

Since upgrading JIRA to version 7.3.6 we have the same problem.

Clearing the browser cache resolves the problem not permanently.

we are seeing this issue now since upgrade to JIRA 7.2.3

Just had this occur to me. JIRA v6.3.13 on Chrome 56.0.2924.67 beta (64-bit)

I am using Jira 6.4.11 and this issue occur very frequently in Chrome 53.0.

Smriti

Hello I'm using v6.4.6 and the problem is appearing :

• Firefox v47.0.1
• Firefox v48.0.2
• Crome v52.0.2743.116

Hello,
Am using 6.3.15 version even am facing the same error in Chrome 50
any fix for this case.

I am using Jira 6.2.7 and have seen this issue in both IE 11 and FF 39.

Timeout while editing project schemes on v6.4.11, using Google Chrome, resulted in an error message pointing to this issue.

I believe it was a simple "Server takes too long to respond" problem as frequently reported for JIRA. This was the first time I saw this message though.

weewewr

Hi! It's still the issue. Win 7, Crome 44.0.2403.130, JIRA v6.3.8

I just had a token-related error message immediately after trying to assign a new issue type scheme to a project, including a link to this issue. [I did have about two dozen JIRA tabs open, I admit]

So erm ... this also happens in Chrome 43.0.2357.81 m. Are you sure it's the browser's fault?

Hi,

We are still experiencing the issue. It looks the bug is not fixed yet.

I experience it now, what is the workaround? when will it be finally fixed?

This problem is not resolved

i confirm this issue is present in latest jira 6.3.7

pnichols104 please open a new JIRA issue for the problem that you are experiencing.

Is there a solution/workaround to this yet? It seems like this may be the problem with my script in jira-python to automatically add users to groups using the add_user_to_group function.

we made,we made all for you

on the back of Brad's conclusions I am making this a conventional JIRA bug and getting it into the bug fix queue.

This issue was created a while back when JIRA 4.0 was created and FireFox 3.6.0 has a definite bug.

People who see this message are not likely to be actually experiencing that exact bug.

what is more likely is that they performed an POST operation that requires login after their session has timed out and the security system (Seraph) kicks in an redirects them to a login page.

After the login Seraph redirects them back to the original URL but this time as a GET and with no data. This is a known problem in Seraph when it "login intercepts" a POST operation.

In terms of fixing this, its is in Seraph that we need to do make this fix.

Same with Chrome 18.0.1025.11 beta on Ubuntu, and also it isn't 5 minutes. Happens even if it only takes 20 seconds to create a new issue. Generally going back and forward in the browser fixes this.

Please fix!!!!

Same problem with JIRA 4.4.3 and FireFox 7.0.1 - Please fix!

The same problem exists in Firefox 6.0.2 Request to fix this

@Monica
@Marcin
@Derek
@Jimmy
It is unlikely that you're experiencing this exact issue - can you please raise a separate issue which includes steps to reproduce & screenshots of the error messages that you receive

This is reproducible in IE 8.0.7601.17514 too.
It happened when I created a sub-task.

Seem to be having the same problem on Chrome 10.0.648.204

I tried with IE 7.0.5730.13 and with Opera 11.10. The same behaviour as in the description.

Please note that I just received this error message while using IE8 - not Firefox

Hi Charles,

Does the "token missing screen" contain a link to this issue? If not, then it sounds like a normal session timeout situation.

Cheers,
Peter

Peter, I do recall seeing the "token missing screen" recently. Next time I see it I'll document it here.

Hi Charles,

can you please confirm whether you're still able to reproduce this one?

Cheers,
Peter

I just experienced this on JDOG and I'm using Firefox 3.6.3 on Linux.

Verifed with QA Bamboo build 351 on FF 3.6.2 on Linux, its fixed.

This has been fixed in FireFox 3.6.2 on Windows.

Additional information about symptoms from Brad:

• In JIRA 4.0, you get an IssueCreate fail error.
• In JIRA 4.1, you get the session token missing screen and a link to this JAC issue when 0 parameters are present.