Bitbucket is no longer able to send Smart Commits, Bitbucket needs to be upgraded

Still need help?

The Atlassian Community is here for you.

Ask the community

Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.

Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Summary

Smart Commits fail intermittently with the following error message thrown on the Jira side:

<Bitbucket_Name> No longer able to send Smart Commits, <Bitbucket_Name> needs to be Upgraded

Environment

Application links between Jira (Cloud or Server/Data Center) and Bitbucket Server/Data Center. 

Diagnosis

  1. Neither recreating the application links nor restarting the Server fixes the issue. 
  2. Inspecting the traffic to your on-premise Bitbucket server, at the Firewall level, does not show blocked traffic coming from Jira. 

Cause

JIRA cached an incorrect status of your Bitbucket Server's capabilities.

Solution

Go to the following link in your Jira (Server or Cloud):

  • http://Your.JIRA.com/secure/ConfigureDevStatus.jspa?projectKey=<PROJECT_ID>
  • At the bottom of the page, hit the "Refresh" button to refresh Jira's cache.
  • Smart Commits should work now.

(lightbulb) For Jira Cloud specifically, if the issue persists, contact the Cloud support team via the Atlassian portal and ask to clear the context cache for your site. 

Last modified on Jun 27, 2023

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.