I am experiencing an issue with the official GitHub for Jira integration where development data has completely stopped syncing to the Jira issue Development panel, and the backfill function is no longer pulling in data.
The Context:
How the issue started: Initially, the integration worked. It successfully synced my very first pull request and displayed it correctly under the KAN-1 ticket. However, any subsequent commits or new pull requests I made using the exact same KAN-1 key failed to appear in Jira.
Troubleshooting Steps I have taken: To attempt a fix, I completely disconnected the GitHub Organization from within the Jira Apps configuration page and then freshly reconnected it.
Since doing this, things have gotten worse:
It seems like the webhook or authorization link between GitHub and Jira is permanently severed for this project, even though the Jira UI says Connected and Backfill Finished.
Has anyone run into this problem before or know how to force Jira to properly recognize the GitHub repository again? Any help would be greatly appreciated!
Hi ,
I have done several of these integration for cloud instances and I haven't heard of anything reported like this. It has been a set it and forget it situation. My usual first thought is to reset the integration which you have done...so, that's a good start.
The next step is to check if Github has logs that you can review to see if what connection or errors pop up. I might provide some indication wether its a API, authentication, or a connection issue. The 2nd thing to do with to raise a ticket with Atlassian support since you are on paid plan.
Thanks,
Ben
Hi @Tej sharma ,
In GitHub → Org Settings → GitHub Apps → Jira → Configure, try to switch from “All repositories” → “Only select repositories”. Save, and then switch back to “All repositories”.
This may enforce a refresh of permissions.
If that doesn't work, can you reinstall it?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Tej sharma
Isn't it similar to your Problem?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.