XSRF Security Token Missing.

[Venkata Rajanna Velichety]

XSRF Security Token Missing.

Jira could not complete this action due to a missing form token

You may have cleared your browser cookies, which could have resulted in the expiry of your current form token.
A new form token has been reissued.

Request URL : /secure/WorkflowUIDispactcher.jspa

The original input has been captured and you can retry the operation.

[Maura Swart · Accepted solution]

We started receiving this message today.  Did you figure-out a solution to the root cause?

[Venkata Rajanna Velichety]

Hi Maura Swart , I dont know the rootcause for this XSRF Token missing.

please help me with this.

regards

venkata Rajanna 

[Maura Swart]

I was able to overcome this issue today by switching to the new issue view; however, our users prefer the old issue view so I don't think they are going to like this answer.

[Joel]

How in gods name is this considered "Solved"?

[Rob Mason]

I am getting this problem for the past 2 days in Jira Cloud when trying to use the 'Move' functionality (to move or change issue type). On the final step (when it should make the change) it gives me this error. Retrying does not fix it.

[Rob Mason]

The same error is blocking me from updating some fields, such as Original Estimate, but I am able to update other fields easily.

When I update Original Estimate it says in a small pop up "We couldn't set the original estimate value" and "You can try again in a few minutes, or refresh the page.".

There is a JavaScript error in the AJAX request in the console. If I look at the response it's just the usual "XSRF Security Token Missing" error.

I have tried clearing absolutely every cache, cookie, storage, session etc and making the browser completely forget about the site, it makes no difference. Yet it works in a different browser.

This is an incredibly frustrating bug with Jira that's been going on for years and greatly impacting my ability to do anything.

[Nena Kruljac]

It happened to 1 of our users (non-Jira admin) too a few days ago while he was trying to move the issue from Task to Story.

The other user was able to do it.

In another issue (in the same project) I (Jira admin) was able to move it.

In another browser the same user today was able to do it (in this another issue).

[Rob Mason]

Five minutes ago I lost the ability to change ticket status. It was something that was previously still working. Maybe it's relating to switching onto a VPN? But now that it's broken and has this CSRF token error, it is permanently broken in that browser and cannot ever work. It just greys out the page and becomes non-interactive.

[Vincenzo Buttazzo]

Some here, but only on Firefox. Tried to clean all cookies, didn't work. Very annoying.

[Nick]

I am getting this as well. I can't move issues or anything unless I switch from Firefox to Safari. It's worrying to see how old this issue is

[Eduardo Rocha]

I'm also experiencing this issue. Can't change the original estimate value.

[Vincenzo Buttazzo]

In the meanwhile it looks like everything works again here.

[Denis Syropushchinsky]

Fixed this problem for me in the following way (may be it's just a coincidence):

1. First checked with empty FF profile - the problem was not there, so it was definitely a data-related problem.
2. Went to Settings - Privacy&Security - Cookies and Site data - Manage data and cleared data for my Jira only (Clearing all data should do the trick as well).

[Lucian Marginean]

I confirm, I had the same issue and clearing cookies solved my problem.

[Rob Mason]

It randomly started working again for me to day. I changed nothing... although my browser did have an update.

[camus_b_li]

I fixed this issue on two PCs.

Add your Jira site to the Allow list of "Cookies" settings in your browser (Edge/Chrome).

Edge: 

Settings -> Cookies and site permissions -> Manage and delete cookies and site data -> Allow -> Add -> {input your Jira site} -> Add

Chrome:

Settings -> Privacy and security -> Sites that can always use cookies -> Add -> {input your Jira site} -> Add

Good luck!

[Tobias]

I am currently thinking about if this is a bug on the side of the browser session or if this is produced on application side?

For now, this workaround worked as expected. 

Best, 

Tobias 

[Brian]

I am now hitting this "feature" in the Backup JIRA function. It starts the baclup and seems to finish it too, however, the GUI barfs and throws this XSRF token missing error, no matter if I'm at Edge or Firefox.
(JIRA 8.5.3)

/Sarcasm
Great work, Atlassian. I am now even more eager to be forced to pay DOUBLE for DataCenter license. You guys "rock" ..........
/Sarcasm

[Priyanka]

Facing same issue since we updated jira to 8.5.3. Any resolution appreciated. Thanks in advance!

[Lou-Guardia]

So I encountered this issue today when trying to clear the default value for Resolution field. The fix I have found for this is to go to the WEB-INF/classes directory and modify the value below from true to false in the jpm.xml file . You will have to restart jira for change to take effect.

[Groundspeak Ops]

Wow, this is the first fix I've seen posted in close to a year.  Thanks!  I'll have to try this out.  What version of JIRA are you running Lou?   

[Lou-Guardia]

I am running 8.3.4. They mentioned changing the jira-config file but I don't even have that so it must be for older versions. 

[Lotto24 AG]

THX a lot!

[Joel]

Not to be a party pooper but essentially you are cutting the tendons on the security provisions in the product to prevent it from throwing the error here. Cross site script detection is a necessity in today's world. Can we get a fix for this rather than just killing safety measures to prevent warning dialogs? 

[Vishal Petkar]

Thank you!!

[Deleted user]

We have the same issue in 8.8.1

Is there a solution/fix for  this?

[Jan1908]

I also encounter this problem, but only when I change the status of a task whilst I am on the dashboard. It happens about 1 in 4 times. The error popup would appear with the question to retry. Retrying mostly works. So for me, it's only annoying. But strange none-the-less.

[Shawn Masters]

Why is this marked accepted? How did you resolve this issue? 

[Shawn Masters]

I was able to resolve this issue by removing extra fields out of the project. 

We had a single project imapcting the users of our instance with this issue, when reviewing the config i found that the project admin had added a large number of fields to the scheme resulting in this error. After removing unneeded fields from the project this issue went away.

Jira Cloud Admin

[Sean]

Please define "large number of fields." 

I have only one user (that I know of) complaining about this error out of about 60 users, so I'm inclined to think it is their browser, or the fact that they need to toggle on and off VPN to access other services. 

We have a large service desk project that requires many custom fields, issue types, and request forms. It would be unacceptable to need to limit those.

[Gallagher IS Licencing]

We have about 15 of our users experiencing this issue.  It mostly happens when we are resolving an issue.  Retrying does work, but it's getting annoying.

We have cleared cache on all our browsers, but it hasn't resolved the issue.

Why is this happening?

[Joel]

Lazyness!

[Steve Ware]

Jira cloud: This was happening for us when CSV issue imports were large(800+) during a migration. We had to break the import files into 200 issues to get around the web page XSRF issues. It also happens very occasionally when the system is under extreme load or processing excessive page content.  

[Nastaran Modarres]

I was able to overcome this problem , using another browser (firefox) . Clearing cache or  changing Cookies settings (in Chrome) didn't help!

[Marko Isola]

I'm facing the same issue with Jira Application (datacenter version) 8.14.1. It started when I added post function to create transition in a workflow.

Post function is "Email user(s) based on attribute in a selected Insight Object" set as shown below. Default assignee is Insight attribute type User.

Sends an email to users from the attribute Default assignee selected from the Insight custom field Used product or service. Sender email address is: foo@bar (default).

So basically it is set as described in here except there's no Condition.

https://confluence.atlassian.com/servicemanagementserver/post-functions-1044784443.html

If I remove that function Issues can be created to project just fine.

[Marko Isola]

I haven't faced this issue since we upgraded from 8.14.x to 8.22.3

[Enjim]

Hi folks, any permanent solution for this? I´m afraid, we´ve got a user that reported this kind of issue this morning. If it happens again, we will have a ticket to solve.

Regards.

[Debbie Jolley]

Just had this error tonight - I'm one of our site admins

Trying to do a Bulk Edit on a Project to populate the Component field - and bam this error occurred

Frustrating to see it's an ongoing issue reported by multiple people with no solution provided

[Kyle Li]

facing the same issue. 

May i know what's your solution for this issue ?

[sandeepvaidya]

I got the error when I was trying to export issues in JIRA or trying to create a test case in XRay.

 The went away when I switched browsers from FF to Edge!

[Hanz Makmur]

I am having the same problem as well. Despite using different browsers, incognito mode etc.   I encounter the same issues.  I have to keep trying multiple times  and 1 of 5 or 6  times it works temporarily and it went bad again. Is there a solution to this? First report is almost a year ago.

[Hanz Makmur]

My fix.

1. Login as admin.

2. Click on top/right cogwheel and select System. Login again.

3. now you can use the Project menu.

Something is buggy !!

[Lucas Stroutinski]

Same problem here only for one of our users, he cannot modify the issue field on multiple projects.
I recognize the Atlassian laziness when they want to "solve" the problem quickly without doing anything , nice one guys ! 

[Martin Krimpelbein]

Same for me! Only getting this error in a specific project.

Other projects dont have this problem. Deleting all unnecessary custom fields does not resolve it!!

Please provide a fix / solution for this.

[dwalliang]

Hello,

After upgrade from Jira 8.2.2 to Jira 8.5.5, we have the same problem.

Still no real solution ?

Regards

[Justin_Gries]

Having the same problem. Retrying the action yields success, but having to deal with this dialogue frequently is unacceptable.

How is this being marked as "Solved"/"Accepted" when no real solution has been defined? Did someone need to get their ticket-queue down?

[Julia_Davies]

I started receiving this error today and I am the sole admin. It renders me unable to do any system updates/configuration changes to try to fix the issue. I tried upgrading to the latest version and it did not fix the issue. Switching to Firefox from Chrome seems to fix the issue. Clearing all the tokens only works until I have to log back in. I am unable to log in unless I check the token to remember my login. I am not in the Cloud, I am in a local install. I don't see a way to switch to a "new issue view". 

The error note "Please refer to this page for details on disabling form token checking." brings me to a broken link. 

[cava cavamagie]

any news?

[xavierConti]

Hello, same problem for me, after upgrade from Jira 7.9.13 to Jira 8.5.4

Still no solution ?

I've found this issue :

https://jira.atlassian.com/browse/JSWSERVER-20347

But no workaround for now...

[Victor Peters]

There's an option in every user's profile to 'Clear All Tokens'.

Have you tried this?

[Priyanka]

Tried this solution, doesn't work !