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.
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.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs