Why Do Commits Not Automatically Sync to Jira When the Branch Name Uses the Jira Key?

[Jordan Carmona]

Basically this:

https://confluence.atlassian.com/adminjiraserver/integrating-with-development-tools-938846890.html#:~:text=repository%20name%3E.-,How%20it%20works,-When%20the%20Atlassian

> Commits are linked automatically if the issue key is included in the commit message.

A commit will only appear "linked" if the Jira Key is in the commit message. The expected behavior from my team (new to Jira) is that by naming a branch with the Jira Key, then all subsequent commits would appear within the linked issue as well.

Why is this not the case?

The options we are looking at include:

1. remembering to input the jira key at every commit
2. creating a pre-commit hook to add in the jira key based on the branch name
3. creating a pipeline to add in the jira key based on the branch name

So basically, human fallibility or creating a stock automation for every one of our repositories?

[Aron Gombas _Midori_]

We use a specific commit policy to enforce work item keys in:

1. Every pull request title
2. Every commit message (unless someone enters "#skip_check")

Not only the key must be there, it also must match a JQL query. It ensures that a work item from a valid project is chosen, the status is correct, etc.

That way, the work item references in our Bitbucket workspace and in our Git history are always precise.