Can a Server-side hook be utilized to update the appropriate Jira Issue IDs for a commit?

[Samir Kabiraj]

Is it possible to utilize any of the server-side hooks to validate and only link the validated Jira Issues to the commit?
As Bitbucket and Jira integrations is done strictly based on commit messages it is possible to enter multiple existing Jira Issues IDs in one commit message. Now that may seem to be valid from the developer's perspective as the same commit may be related to more than one Jira Issues. But that also opens the possibility of entering incorrect or already completed (Done) Jira issues. Most of the time developers enter the correct IDs but when they enter an already completed Jira Issue ID that creates a headache for the release team. We are looking for validating the status of the Jira Issue IDs and link the correct IDs only to the commit and ignore the incorrect IDs. So, we are looking for a programmatic (curl etc.) way to establish the Jira and Bitbucket integration using any of the server-side hooks.

[Julius Davies _bit-booster_com_]

Our "Control Freak" app does exactly this (rejects commits that refer to invalid Jira ids).

https://marketplace.atlassian.com/apps/1217635/control-freak-commit-checkers-and-jira-hooks-for-bitbucket?hosting=datacenter