403 error when loading Jira issues

[Marcus Ragaller]

Atlascode v2.10.1
VS Code v1.63.2
OS MacOS Big Sur v12.1

If I open Jira in the sidebar all filters return “No issues found”. If I open the Jira settings interface I get the error in the screenshot below.

The output panel has the following error: error refreshing token Error: Request failed with status code 403

I have uninstalled the extension and I have signed out and back in and the issue persists.

[Marcel Borg]

I am experiencing the same issue

[Juan Hurtado]

Same here

[Jonathan Doklovic]

@{5fe45e23f7ea2a010738d376} @{557058:d08891e0-f92d-4579-9f08-475258940e7c} I was able to re-create and resolve this by simply re-authenticating with Jira.

Can you open the “Atlassian Settings” screen and simply click “Login to Jira Cloud” on the Jira tab and go through the auth flow again.

Let me know if that works.

Thanks!

[Marcus Ragaller]

@{557057:3695b794-cde3-43a2-99aa-c0fc6151b754} re-authenticating resolves the issue temporarily. The errors reappears after relaunch of VS Code and sometime even during the same “session", i.e. without restarting my machine.

[Marcel Borg]

When I try that I get the below:

‌

[Jonathan Doklovic]

Yeah, you can’t auth remotely. You need to auth in a local instance and then the remote will use the new auth details.
FWIW, we have identified the bug and are looking into possible fixes

[Marcel Borg]

Yes - sorry I realised that as soon as I sent that. That seems to have worked for me.

Hopefully it’s not a temporary fix for me like it is for Marcus.

[Marcel Borg]

Thank you!

[Marcus Ragaller]

@{557057:3695b794-cde3-43a2-99aa-c0fc6151b754} fantastic - that is worth quite a bit!

Happy to re-auth, so long as I know a fix is being worked on!

[Nick Rundquist]

We’ve released version 2.10.2 which should fix this issue. It should just work, but it’s possible that you’ll need to log in one last time to get everything working correctly. Let us know if you’re still seeing issues.

[Marcus Ragaller]

I’ve just re-authed and it seems to be working (the 403 error in the settings page hasn’t shown its face)

Thanks for the quick response!

[Marcus Ragaller]

Issue appears to be resolved with v2.10.2

[Ivor Paul]

I needed to uninstall and install the extension again and also remove the the previous integration with the trash icon on the Atlassian repo settings page. Not sure which one of those two helped. Thanks for the quick fix!

[Marcus Ragaller]

I only binned the integration (authentication) “profiles” and re-authenticated. No reinstallation needed.