Verifying branch names - DONE! Levente Szabo August 16, 2018 07:54 Follow To enforce naming conventions typically. Have more questions? Submit a request 3 Comments Date Votes 0 George Ivanov September 20, 2017 12:15 Currently, the rules logic allows us to match commits (in one form or another) against issues. That’s fine, but it doesn’t give us any control of the branches creation. In BitBucket, branches are usually created for a particular issue/story, but this add-on cannot restrict this or make it as part of a policy (we could type, “ZZZ-1” as a branch for example, which isn’t a valid issue). We currently use another add-on that restricts branches only to a particular workflow (the git workflow), but the problem is, it cannot check for valid issues (only their format) when creating those branches. It would be nice if we could have the restriction described above that places a check on branch creation to make sure it is mapped to a valid issue (and their corresponding JQL) only. This will give us complete control of what we need to do and we will only use a single add-on through which to enforce our policies. 0 Ferenc Nagy August 16, 2018 07:49 We are happy to announce that verification of branch names is now possible since Commit Policy Plugin for Jira 3.0.0! Update your add-on from the Atlassian Marketplace and read more about what's new in the release in the release notes. Thanks everyone for your continued interest and patience! 0 George Ivanov August 16, 2018 07:54 Already using this. Thanks for implementing it. Please sign in to leave a comment.