nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

bitbucket commits with jira-key bug

Oussama Baaziz

hello,

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.

thanks

Accepted answers

Theodora Boudale

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.