Iterated PRs is the percentage of merged pull requests that have at least one follow-on commit.
In this article
Which reports use Iterated PRs?
You can see Iterated PRs in Team health insights.
What does Iterated PRs measure?
The Iterated PRs metric helps you see how many of your team’s submitted pull requests require additional work before being merged.
A high percentage of iterated pull requests could indicate that the initial PR is lacking in quality or is not aligned with requirements.
How is Iterated PRs calculated?
Iterated PRs is calculated as the total number of pull requests with a follow-on commit divided by the total number of pull requests.
The follow-on commit can be made by either the pull request submitter or a reviewer.
What data is included in Iterated PRs?
A pull request counts toward Iterated PRs if it is a merged pull request.
Pull requests are not counted toward Iterated PRs if:
- they are created by a user who is excluded from reports
- they are created by a hidden user
- they are an excluded pull request
- they are from a deleted repository
Note: User view rights and permissions also impact how specific users will see Iterated PRs.
If you need help, please email Support (opens email form) for 24/7 assistance.