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 commits with jira-key bug


i have a repo (i am the owner) at Bitbucket linked to a Jira project. with the Require issue keys in commit messages enabled,all was working well,

i transferred ownership of the repository to our workspace , after changing my remote in local GIT my commits push where blocked by bitbucket, saying no issue key found in commits, but my commits had them. 
turned out the link between Bitbucket and Jira broke,  so bitbucket don't know the key anymore,

the bug is that you can't disable "Require Issue Keys" . 
the button is disabled (html disabled), because there is no link in the list . but it is disabled on a True State (green disabled button).
i had to manually inspect the button,  remove the HTML disable, turn it off, push my work to Bitbucket. and re link my projects again.

don't know if this is intended or a bug worth reporting.



1 answer

1 accepted

0 votes
Answer accepted

Hi Oussama,

Thank you for reporting this issue.

I have been able to reproduce this behavior, when the target workspace does not have an integration with JIRA. If there is an integration between the target workspace and the same JIRA instance, this option can still be disabled/enabled.

I went ahead and opened a bug report for this in our issue tracker:

for our development team to take into account.

If you have any questions or need anything further, please feel free to let me know.

Kind regards,

BCLOUD-20440 has now been fixed.

Like # people like this

Suggest an answer

Log in or Sign up to answer
Site Admin

Atlassian Community Events