Using a Fine Grained Github PAT Token with Tasks & Contexts
I rely heavily on the Tasks and Contexts feature as part of my workflow. I have been using it with Github, configured with a classic access token, however my company have moved to only allow fine grained access tokens.
When I set the API token field to use a fine grained PAT, the Test button indicates success, but when I try to search for tasks, an error pops up with ‘422 Unprocessable Entitry - Query must includee ‘is:issue’ or ‘is:pull-request’
Any idea how I can get this working again?
GoLand 2025.2.6.1
Build #GO-252.28539.64, built on April 22, 2026
请先登录再写评论。
Thank you for the report. Could you please reproduce the issue, collect the IDE logs via Help | Collect Logs and Diagnostic Data and upload them to uploads.jetbrains.com? Then share the upload ID with us. The logs will be accessible only to JetBrains employees. The logs should give us more insight into what's happening.
Hi Svetlana, I've uploaded the logs and diagnostic data, as well as a screenshot if the error notifications.
The upload ID is 2026_05_25_CeK67pTMeq9TkzzB5XwXUS
Thanks,
Noel
This looks like an issue users faced in the past, some reported that they do not experience it inside 2026.1 anymore. Does upgrading to 2026.1 help?
Best regards,
Uros Glogovac
IntelliJ Support
I upgraded to 2026.1 and it made no difference unfortunately
Can you please share logs? We would like to inspect the stack trace to see if the same exception is firing. Thank you!
Best regards,
Uros Glogovac
IntelliJ Support
Actually, it does seem to sort of work?
After opening `Switch to Task > Open task` it seems to perform a search of Github issues and once the search is complete I can then filter by issue number. However, it always shows a ‘Cannot connect’ notification with ‘422 Unprocessable Entity’ as soon as I start typing in the dialog box, see 2026_05_29_CT5yig6j8YVbpHBZ5WG8Yj
The UX on this feels strange. I don't see a way to refresh issues from GH and typing in the issue ID of a new issue doesn't seem to force a refresh.
Logs & diagnostics are at 2026_05_29_8SEM2WZ6gGqLHEaFwxTH66
Thanks for the logs! This is a known issue we are tracking here: https://youtrack.jetbrains.com/issue/IJPL-175193
Please star it and up-vote it to track any updates.
Best regards,
Uros Glogovac
IntelliJ Support
Thanks for pointing that out, tracking.