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.
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.
Hi everyone, We are looking to learn more about development teams’ workflows and pain points, especially around DevOps, integrations, administration, scale, security, and the related challeng...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events