Check in Approval process

How to enable the Rule check-in approval process for Branch ruleset .

Branch rulesest will be created once any rule is created in that branch . so do we need to wait for same to apply approval required field.

It should be available on branch itself as optional , so that any new branch ruleset will be created , will have default Approval flag required.

Please suggest if any other way to do that.


Keep up to date on this post and subscribe to comments

January 12, 2019 - 1:18am

Thanks for link , but i have already checked this before. but it does not say about the branch rulesets.

January 26, 2019 - 12:49am

Still waiting for Answer

January 31, 2019 - 12:23pm

Checkin approval process does not tie into Branched rulesets, however starting in 7.3, there is a Branch Review feature that has been implemented. There are flags that can be set such that if the branches are unreviewed then merges are not allowed on the branch. This should provide a similar workflow to the checkin approval.

February 2, 2019 - 4:39am
Response to Linoy Alexander

Yes, I am already aware of that feature , but that will still not hold  the check in, merge will be blocked.

February 5, 2019 - 9:50am
Response to Mukesha0

When using Branch based development pattern, the individual checkins have been emphasized less, as it is likely the review needs to happen on the entire change set that will be in the branch.  Best practices for branch based development would include

  • Ensure that branches are short lived, it should only be associated with the story of bug, merge as soon as that work is done and reviewed
  • Ensure that the changes introduced in the branch are off high quality, leveraging the branch quality landing page
  • Review the entire change done in the branch - using the branch review feature

Given this workflow, the rule checkin approval is not as relevant as we see it.