Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Bitbucket Cloud connection to Jira Datacenter

Benjamin Newton
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Apr 18, 2023


We're attempting to connect our JIRA Datacenter instance to our Bitbucket Cloud repository.

We've set things up following these instructions:

However, that does not seem to allow us to link our pull requests/commits to JIRA issues, and these cloud instructions do not seem to apply to datacenter:


Is there a way we can see our Jira datacenter issues in our bitbucket cloud repo?

1 answer

0 votes
Theodora Boudale
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Apr 19, 2023

Hi Benjamin and welcome to the community!

A common cause for this issue is permissions:

Project permissions required

Project users must have the 'View Development Tools' permission to see commit information in the Development panel in a Jira Software issue. A Jira Software admin can edit a project's permission schema to grant this permission. See Managing Project Permissions.

If these permissions are ok, we would need to review your setup to further investigate. I see that you already created a ticket with the support team, so I would suggest focusing on the ticket in order to avoid any confusion and miscommunication that may arise from troubleshooting the same issue in two different places.

Once the issue is resolved, feel free to share here the resolution for any other users that may come across your post facing the same issue.

Kind regards,

Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events