auto-populate ticket id on commit

[Mike Hedman]

So, I maybe just a bit crazy here. But it seems wierd that I have to put the ticket number in the commit notes, for a branch that was created against the ticket.

We have a number of developers all over the world, and we are struggling with people having typos with their ticket number when the write commit notes. They either typo the wrong number, and now that commit is nearly forever (ie, difficult to move back) associated with the wrong ticket. Or they type in a wrong ticket number that doesn't exist. Welcome la la land.

Are there any pluggins or setup configurations that would auto-associate to the ticket it was branched from when a commit with no ticket number is listed? Then I can tell the devs, only when you specifically want to associated a commit with a ticket that it wasn't branched from, you type in the ticket.

[Mike Hedman]

And we are using sourcetree to do the checkins. For me, the big issue is that if someone fat fingers the ticket number, and puts their commit against my ticket, and then has a code review pending, my ticket can't move forward until that code review is completed. We haven't found a good way to "move" commits around if they get pushed under the wrong ticket.

[Seth]

Ok, I fixed the tags. Hopefully someone familiar with Jira and/or Stash knows about an alternative way to associate tickets with commits.

[Mike Hedman]

we use jira and stash. I probably do have the wrong tag associated with it. And we use sourcetree to do commits.

[Seth]

SourceTree seems like an irrelevant tag here. Ticket-commit associations don't occur in Git/Hg, they occur in the various ticketing systems out there. What are you using on that end?