I have a recent issue that started at the beginning of this last week of November, 2021.
I use Jira (Jira Clouds for Sheets) integration in Google Sheets to extract data and do automations. This search always worked normally, but now it's showing this "no site selected" error (picture attached below) in the cell of the spreadsheet that the search is being done on.
Can anyone tell if there has been any change in permissions? Any new updates that prevent Google Sheets from working the API?
I haven't found anything about it anywhere!
Hello @mateus_santos ,
It looks like Google Sheets is having an issue reconnecting after an auth token expiration.
To correct this open the Jira Cloud for sheets Extension in the sidebar of your sheet by going to Extensions >> Jira Cloud For Sheets >> Open and select the "Disconnect site" option towards the bottom of the sidebar:
This should disable that app in the sheet and then redirect you to the following link on the Atlassian Identity platform where you will want to select the Disconnect option for the "Jira Cloud for Spreadsheets" app, located under the "Apps with access to your accounts" section:
After the site is disconnected go back to your sheet and go to Extensions >> Jira Cloud For Sheets >> Open then go through the steps to authenticate to the site and you should be all set with a manually refreshed authentication token for the connection.
Let me know how it goes.
Thanks for the support, I followed exactly these steps and managed to solve! There really should be something wrong with the expired access token!
For those of you who still haven't managed to resolve this issue, please update your status on this issue here! My theory is that it could be something related to the creator/owner of the spreadsheet that needs to do this for the token reset to work, but I believe that only with tests it is possible to know.
I've been in contact with the Jira cloud for sheets Dev team and they just pushed an update on the backend that should help out here and fix the Deauthorization issue causing the sheet to disconnect from Jira.
At most, any affected user should only have to re-auth to Jira once as defined in the steps listed in my comment earlier (if you were deauthed before this new release was pushed out), but you should not lose auth subsequently.
Please retry the manual reload process I noted earlier and I would also recommend a cache flush on the browser before doing so as well just in case something is getting held onto in the cache that is causing additional failures in the background. let me know if you see any issues with repeated deauthorizations from here on out and we'll take a closer look.
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event