Jira to Github integration no longer working

[jennifer_mitchell]

As of earlier today our jira tickets are no longer showing the branch or PR information under the development section. 

We have checked all of our connectors and permissions and nothing seems to have changed. 

Is there anything else that we can check to ensure this connector is working as intended?

[Michael Kreitz]

Yep, same with us. Didn't change anything. Experiencing same issue as the others. We opened a case with Atlassian yesterday, but they have not provided any helpful information so far, despite us escalating with them. 

[Michael Kreitz]

Just received word from Atlassian that they are working on fixes on the backend, 3 of 4 fixes are completed. If that information has not been shared with the rest of those experiencing the same problem, I hope it helps.

[Joel Wadagnolo]

We are experience this at our company as well as of yesterday (around noon PST).

Our connections are with BitBucket (Both our Cloud and Datacenter instances of BitBucket) but it sounds likely that the same issue is affecting both GitHub and BitBucket integration.

[Joel Wadagnolo]

Okay, it looks like Atlassian has fixed the issue. I came in this morning and I'm seeing branches/PRs showing up on Jira from both BitBucket Cloud and BitBucket Datacenter.

Automatic transitions I had setup also triggered as expected (for us specifically to transition Jira tickets from NEW to ASSIGNED when it sees a branch).

[Richard Horace]

Experiencing a similar issue with Jira Cloud to Bitbucket Cloud.  Branch gets created but does now show up in the Developer Section.

[Ankita Mehta]

Hi @jennifer_mitchell

If your Jira tickets suddenly stop showing branch or PR info but nothing’s changed with connectors or permissions, here are a few things you can check:

• API tokens and permissions — Sometimes tokens expire or lose some access without obvious changes, so double-check those just in case.
• Service status — It’s worth seeing if Jira, your source control system, or any middleman service is having outages or issues.
• Sync logs — If your integration tool offers logs or dashboards, take a peek to see if any errors popped up.
• Platform updates — Occasionally Jira or your SCM updates their APIs or webhooks, which can impact integrations.
• Webhook delivery — Make sure the events for branch or PR creation are still being sent and received properly.

It’s also a good idea to have integration setups that handle retries and errors automatically to keep everything running smoothly without manual fixes. For example, you may want to consider enterprise – grade integration solutions like OpsHub, an Atlassian Silver Solutions Partner, that can help manage these complexities by providing more robust sync handling and error recovery, deep data sync helping eliminate interruptions from these kinds of issues.

Here is the link to our GitHub and Jira integration page on Atlassian marketplace, if you want to kind of check in further

Hope that helps! Let me know if you want to dig into any of these steps.

[Javier Pozuelo -Exalate-]

Hi @jennifer_mitchell I'm the community manager at Exalate.

Welcome to the community!

It looks like there may have been a related outage (given Atlassian’s status updates and GitHub’s incident history), so opening a support ticket might be the safest bet.

That said, if this sort of disruption happens often in your workflow, it could be worth looking into some Marketplace alternatives for GitHub–Jira integration. Different apps take different approaches — some are simple one-way links, while others (Exalate included) provide more flexibility, like syncing across multiple GitHub repos or handling issues, pull requests, and comments bi-directionally.

Hope this help!