Dataset: Issues & Pull Requests
Entity: Pull Requests, Issues
Field ID: last_peer_comment_at
Type: Datetime
Description: The datetime of the last comment made by someone other than the author, excluding bots (e.g. CodeRabbit, Dependabot).
Source: Calculated
Transformation logic: It is the creation datetime of the last peer comment on the issue or pull request. A peer comment is a comment whose author is known, is not the author of the issue or pull request, and is not a bot, as Author type defines it. First peer comment at describes the rule in full. The field is empty when the item has no peer comment.
App Mapping
GitHub (PRs, Issues) | Calculated |
GitLab (MRs, Issues) | Calculated |
Bitbucket (PRs) | Calculated |
Azure DevOps (PRs, Issues) | Calculated |
Jira (Issues) | Calculated |
ClickUp (Issues) | Calculated |
Trello (Issues) | Calculated |
Reporting Use Cases
The last_peer_comment_at field marks the end of the human discussion on a piece of work, leaving out the comments bots keep adding after each push.
Length of the review discussion:
(last_peer_comment_at - first_peer_comment_at) / HOUR()gives how long teammates kept discussing a pull request. A long discussion on a small pull request often points to an unclear requirement.Time from last feedback to merge:
(merged_at - last_peer_comment_at) / HOUR(), filtered onstate == "MERGED"andIS_NOT_NULL(last_peer_comment_at), shows how long pull requests wait once the conversation is over.Stale conversations: open items whose
last_peer_comment_atis more than a week old have had no human attention since, whatever bots may have posted.
