I see some help pages on here asking for something similar, but I can't seem to find anything regarding enforcing Jira IDs in Visual Studio Team Services in Git mode's commit messages. Has anyone attempted to enforce that when utilizing a tool like Jira Git Integration? Yet Another Commit Checker seems to only support BitBucket. Ideas?
If you're using TFS on-premises, there's an option for deploying an add-in to do this. You can also do the enforcement on the client side as well.
The thing that doesn't have an option available is to do this on the Visual Studio Team Services online --- there's no hook or API support for failing a commit because it doesn't meet pre-conditions.
Is TFS on-premises OR client side enforcement an option for you?
So there's two levels of checking that can be done...
There's a real check where the issue must really exist and the Jira API is checked to make sure.
What a lot of people do is just check the message to see if it's likely it has a Jira issue referenced: ABC-1234 (even if ABC-1234 isn't a real Jira issue). The advantage to that is there is no API check, so you don't get into Jira credentials or Jira problems causing TFS to fail commits.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Trello is one of the most effective tools for driving your sprints. It's customizable for every Agile team and product owners and Scrum masters (SM) love it. However, Agile teams often struggle with:...
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