Git Notes should contains JIRA issue link

Question

The subject says it already:
Can Bitbucket extract information about a JIRA issue from the Git-Notes?

Because: If a JIRA ticket is mentioned in the commit message, then it is displayed once in the column "Message" and also in the column "Issues". That's redundant information.

Benefit: You have the possibility to link commits to JIRA issue additionally or with more JIRA issues together.

But JIRA issue page also have to extract the information correctly - which it doesn`t do.

Jan Runte · Answer

Why we cannot preserve this connection (commit <=> jira issue) after the issue branch removal?

The Git Notes are the only way to add information to a commit without rebase your git history. and it is a good approach in my opinion.

It will be nice when bitbucket on the commits page also evaluates the Git Notes to link to the jira issue (why were these changes made?).

And vice versa: The jira issue page can find out which commits was needed to fix that issue.

Next point: Issue branches are not always created to fix bugs, and you can not guarantee (as a template or via git-hook) that you will always put the issue information in commit messages.

From me there can also be a plugin for it. But found nothing.

Any suggestions?

Alexey Matveev · Answer

I think issue branches must be merged to the master branch or develop branch before deletion. In this case you will still see the commits.

Jan Runte · Answer

You lose the commit history for a JIRA issue when the branch is removed.
Only if you annotate the commit message with a JIRA ticket the commit history will be preserved.

I also want this behavior/feature for Git-Notes, not for Commit messages only.