We've been using this for months now and it works great 99% of the time. The 1% that isn't great is when a developer forgets to put the id in the comment or the pr title.
The way we want to solve this problem is by creating a custom status policy that examines the source branch (feature/TST-123) and checks if that appears in the pr title or description or comments of any of the commits. This seems like such a common problem that I wanted to suggest adding it to the project so that everyone can get it instead of everyone having to implement it and in slightly different ways.
Obviously, the branch has to fit the pattern and be found in Jira before it becomes active. From there an admin will only add it as a required policy where it makes sense. For us, this would only be on PRs targeting the master branch.
sefi-jwilliams
commented
4 years ago
We've been using this for months now and it works great 99% of the time. The 1% that isn't great is when a developer forgets to put the id in the comment or the pr title.
The way we want to solve this problem is by creating a custom status policy that examines the source branch (feature/TST-123) and checks if that appears in the pr title or description or comments of any of the commits. This seems like such a common problem that I wanted to suggest adding it to the project so that everyone can get it instead of everyone having to implement it and in slightly different ways.
Obviously, the branch has to fit the pattern and be found in Jira before it becomes active. From there an admin will only add it as a required policy where it makes sense. For us, this would only be on PRs targeting the master branch.