Control Freak Bug

[Andreas Pohl]

Hi,

We’re facing a problem with Control Freak (v2024.09.17) on Bitbucket DataCenter (v8.19.9).

We have activated the rule in Control Freak that checks whether Jira tickets referenced in commit messages have a valid status (e.g. not “Done”) and we have the following misbehavior:

1. Developer A creates a local feature branch, makes changes and pushes them
2. Developer A creates a pull request
3. The pull request is being reviewed and merged
4. Developer A closes the associated Jira Ticket
5. Developer B pushes an unrelated feature branch with local changes based on an older master commit
6. Developer B merges the current master into their feature branch
7. Developer B tries to push that update
8. Control Freak declines the push since the Jira Ticket referenced by Developer A has an invalid status ("Done")

As a workaround, we are currently deactivating this check, but would like to have it in place to prevent an incorrect Jira ticket from accidentally appearing in the commit.

We can't say whether Control Freak has only recently started behaving like this or whether this is actually the first time we've run into this situation. However, given the number of pushes, it would be surprising if we had never been in this situation before.

Best Regards

Andreas

[Julius Davies [bit-booster.com]]

Sorry for the delay responding - we have reproduced this issue, and Control-Freak’s behaviour is definitely not correct. We’re actively working on fixing this and we will provide an update soon, as well as information about when this incorrect behaviour started.

[Julius Davies [bit-booster.com]]

Fixed in v2024.10.05 (which was just published) ! Couldn’t have fixed it without your bug report. The steps you included were invaluable.

The problem was caused by a regression in v2024.07.10.