Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Link Bitbucket Server to Jira Cloud

Jerry Kowalewski March 18, 2019

I've tried just about every faq, forum and guide, but still cannot get Bitbucket server to link to Jira. The actual linking process works, and says Connected on both sides, but if I go to a Jira software Issue, I see this on the right side: 

JIRA is having difficulty contacting Bitbucket. If this condition persists, please contact your Jira Administrators.

Is there anything else I can check? I've tried reinitializing the connection about 3x by deleting from both sides, then initializing from bitbucket first, then the next time from Jira cloud first. Neither order seems to make a difference.

I missed being able to use the wizard at first run of Bitbucket as I skipped it. Is there anything else I can do, or check to make sure I've configured this properly? Are there any open ports required for this to work on the Bitbucket server side aside from https?

Lastly, I just noticed that I have an old, un-used bitbucket cloud trial account. Could that be causing this issue? in trying to link to bitbucket server? If so, how do I remove the bitbucket cloud trial?

Thanks!

1 answer

1 accepted

0 votes
Answer accepted
Jerry Kowalewski March 19, 2019

I found the issue... it was quite hidden to be honest. I had to navigate into each project's settings, then to Summary, and had to add the application link there to each project. In fact, the first time I did it it showed a small yellow yield sign and stated: Configure two-legged authentication (2LO) on this application link to use missing features. Once I added the link there it worked.

I could not find any reference to this on the community or documentation. Maybe I was looking in the wring spot, but its worth mentioning.

Scott Taylor March 20, 2019

I am seeing a different problem, but under the same banner (Connect Bitbucket Server to Jira Cloud).  I launch Bitbucket Server, navigate to Application Links, and create a link to Jira.  It's status is Config Error, because it hasn't connected to Jira yet, as authentication on the Jira side hasn't been set.  I then log into Jira, and create an Application Link to Bitbucket server, but when I set the connections in Jira to OAuth and then click Save changes, I receive this error "We can't enable the incoming authentication because Bitbucket is not reachable.".  However, I am working in the same browser on the server I am using to to install and configure Bitbucket Server.

No idea how to get beyond this issue.

Jerry Kowalewski March 20, 2019

When I had this issue, I found that it helped to have both Bitbucket server and Jira Cloud logged into and open in the same browser with the admin user in both systems. When you then create the Application link in Bitbucket, it should automatically send you to Jira cloud and create the reciprocal link for you, no intervention required.

The last step, which I stumbled upon was after this, in my Activity Stream on my Jira cloud System Dashboard, I noticed an authentication request notice showed that required me to approve the application link request. Perhaps this is it?

Scott Taylor March 20, 2019

I figured that part out, as well.  However, I am unable to get Jira to verify the connection to BbServer.  I am trying to use http://localhost:7990.  Firewall is not an issue.  Did you use an external IP in the Jira application link to BbServer?

Jerry Kowalewski March 20, 2019

Yes, I use an external IP. Actually I switched to a DNS A record in case the IP ever needs to change, I just change it in my hosted DNS.

Scott Taylor March 20, 2019

So you created a public A record, pointing to a public IP, nat-ed that through your firewall to an internal IP that is associated with your BbServer server?

Jerry Kowalewski March 20, 2019

That's correct, would need port forwarding if behind a hardware firewall. Localhost would not work since Jira Cloud cannot resolve that. Your Bitbucket base URL would need to be updated accordingly after making the adjustments. Since you are public facing when using this integration, you should definitely configure and use SSL.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events