Commit messages in our organisation are supposed to include the Jira Ref. But some dont. This means that the links we have between Jira stories and Bitbucket commits arent made. Is it possible to amend these after they have been committed and pushed to the repository event to get the links in place?
Generally speaking, it's discouraged to alter Git commits that are already published (pushed to a repo from which your team mates may have pulled those in the meanwhile).
The correct workflow is to require the issue key before the commit is created!
That means that if you try commit without entering a valid Jira issue key in the commit message, your commit should be rejected.
This supports this workflow: https://marketplace.atlassian.com/apps/1214430/better-commit-policy-for-bitbucket?hosting=server&tab=overview
Yep That is the correct course of action (Require a correct format on commit messges) and wouldn't it be wonderful if that was in place in our organisation?
Sadly it isnt and so We are where we are; with a shed load of commits that dont link back to the Jira Stories.
Reprimanding the Developers - telling them that they are very naughty doesnt fix the issue.
Sorry this doesnt fix the problem.
We need to change what has already happened.
Some more ideas:
Hey Community! We’re willing to wager that quite a few of you not only use Bitbucket, but administer it too. Our team is excited to share that we’ll be releasing improvements throughout this month of...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events