Jira Cloud for Sheets - getting no jira auth error

[Yuliia Levchenko]

Hi all,

JIRA Cloud of Sheets was working normally previously for my Google sheet, but today when trying to extract data it shows me "no jira auth" error and a blank panel.

All functions are enabled http://prntscr.com/12f3jtz

I even tried to disconnect and connect the site once again but without luck. All formulas look correct.

Interesting that when I made a copy of file and execute the same steps, everything works fine.

Could you please advise what can be an issue or what else should be checked on my side?

Thanks

[ecoulon]

Hi, I experienced the same issue. After trying different things such as uninstalling/reinstalling etc., what made it work again was from the Google Sheet to go to "Extensions" -> "Jira Cloud for Sheets" -> Open. You'll see a widget on the right, where you can disconnect/connect to JIRA. That fixed the "no jira auth" issue when using the "JIRA()" function. Thanks.

[Sergey Kurguzenkov]

Faced the same issue, and found out that Jira Cloud for Sheets works correctly only when authorized in Jira on the behalf of the owner of the google account. If you have editing rights and authorize in Jira, then that gizmo will show whatever error from jira no auth (though JQL works, and it fetches some data from jira) and syntax error to Jira - unkown function. Truly misleading.

Solution that worked for me - create a new google sheet in your google account, copy-paste the data (or simply the formula), revoke the Jira Cloud access (if any), give it again, disable and enable the JIRA function switch on the Get issues from Jira tab.

[Earl McCutcheon]

Hello @Yuliia Levchenko ,

Thanks for reaching out, and the error "no jira auth" can have a few different causes but it is going to be tied to the google authentication token being interrupted or blocked in some way.

The first thing to check is for a local browser issue, check out the KB article "Browser Troubleshooting Guide" under the "Indispensable tests" section.   With a primary focus on the options to try logging into your Sheet from another browser and/or Incognito mode, as well as flushing cache.

Next, make sure the browser is up to date with the most recent version, and log out of the Browser, and then log back in to establish a new authentication token.

Then verify the document owner, and try changing the owner if there is a known issue with the current owner's account.  Alternatively, try creating a new document where you are the owner to verify if the issue exists in the specification sheet.

Let me know what you find while testing.

Regards,
Earl

[dinesh.ck]

Hello @Earl McCutcheon  

I'm facing the same issue. Asked a few of my colleagues to refresh the sheet in which I'm having the problem and everyone got the same error. It had been working fine for a couple of months. Making a copy of the sheet works. I tried disconnecting, disabling and re-enabling JIRA() but didn't work. Also, tried by uninstalling and re-installing JIRA Addon. 

Regards,

Dinesh

[Stephen Sifers]

Hello Dinesh,

Thanks for reach out about this issue. From what you stated about Copying the sheet allows it to start working which leads me to believe the original sheet is having an issue with the 'owners' token and thus not working.

For the original sheet, could you verify or change the owner and let us know if that allows it to start working?

Regards,
Stephen Sifers

[dinesh.ck]

Hi @Stephen Sifers 

Thanks for your response. I got ownership moved to me and still facing the same issue. After transferring ownership to me I even tried by disconnecting and then reconnecting. 

Regards,

Dinesh

[dinesh.ck]

When I pull data in the same sheet through JQL (in place of JIRA()) it works but I need JIRA() to work in my sheet. 

[José Taveira Gomes]

Hey guys

Me and my team are also facing this issue. We tried all the workarounds mentioned previously but none of them worked. It seems that everyday, we need to re-authorize the Add-on in our Jira. Copying the file to a new one worked only for a few hours, then we had to re-authorize the Add-on again. Any ideas?

Regards,

José

[Giuseppe D'Angelo]

I am facing the same issue, what it has been suggested is a valid work around.

However that's not resolve the definitive resolution.

Maybe it's better to raise our voice again