Keypup

Dataset: Reviews from pull requests

Description: The datetime at which the review was last updated.

The <code>Updated At</code> field from the Reviews dataset is a specialized timestamp that records the last time a review was modified after its initial submission, for instance, if it was edited or dismissed. Its primary use is for auditing and tracking changes to the review record itself.

Filtering for Changed Reviews: You can use this field to find reviews that were altered after they were first submitted.

- To create a report of all edited reviews, you can use a formula where <code>Updated At &gt; Submitted At</code>. This is useful for auditing purposes, especially to see if feedback was changed or clarified.
- To find reviews that were recently dismissed or changed, you can use a filter like <code>Updated At in the previous 7 days</code>.

Analyzing Time to Update: You can measure the time between a review's submission and its subsequent modification to understand how and when feedback evolves.

- A custom formula like <code>(updated_at - submitted_at) / DAY()</code> can calculate the "time to revision." A short duration might indicate a quick correction, while a long duration could be the result of a review being dismissed much later in the pull request's lifecycle.

Distinguishing from Core Timestamps: For all standard reporting on review cycle times and throughput, the <code>Created At</code> and <code>Submitted At</code> fields should be used. The <code>Updated At</code> field is reserved for the specific use case of tracking modifications to a review after it has already been completed.

- Filtering for Changed Reviews: You can use this field to find reviews that were altered after they were first submitted.
 - To create a report of all edited reviews, you can use a formula where <code>Updated At &gt; Submitted At</code>. This is useful for auditing purposes, especially to see if feedback was changed or clarified.
 - To find reviews that were recently dismissed or changed, you can use a filter like <code>Updated At in the previous 7 days</code>.
- Analyzing Time to Update: You can measure the time between a review's submission and its subsequent modification to understand how and when feedback evolves.
 - A custom formula like <code>(updated_at - submitted_at) / DAY()</code> can calculate the "time to revision." A short duration might indicate a quick correction, while a long duration could be the result of a review being dismissed much later in the pull request's lifecycle.
- Distinguishing from Core Timestamps: For all standard reporting on review cycle times and throughput, the <code>Created At</code> and <code>Submitted At</code> fields should be used. The <code>Updated At</code> field is reserved for the specific use case of tracking modifications to a review after it has already been completed.

Reviews > Updated at

Find answers and get help from Intercom Support and Community Experts

This site employs cookies and other technologies that we and our third party vendors use to monitor and record personal information about you and your interactions with the site (including content viewed, cursor movements, screen recordings, and chat contents) for the purposes described in our Cookie Policy. By continuing to visit our site, you agree to our {websiteTermsLink}, {privacyPolicyLink} and {cookiePolicyLink}.

This site uses cookies and similar technologies ("cookies") as strictly necessary for site operation. We and our partners also would like to set additional cookies to enable site performance analytics, functionality, advertising and social media features. See our {cookiePolicyLink} for details. You can change your cookie preferences in our Cookie Settings.

We use cookies to make our site work and also for analytics and advertising purposes. You can enable or disable optional cookies as desired. See our {cookiePolicyLink} for more details.

Advertising cookies are set by our advertising partners to collect information about your use of the site, our communications, and other online services over time and with different browsers and devices. They use this information to show you ads online that they think will interest you and measure the ads' performance. Social media cookies are set by social media platforms to enable you to share content on those platforms, and are capable of tracking information about your activity across other online services for use as described in their privacy policies.

These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.

These cookies are necessary for the website to function and cannot be switched off in our systems.

These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site.

You have the right to opt out of the sale of your personal information. See our {cookiePolicyLink} for more details about how we use your data.

Your Privacy Choices

We use cookies to enhance your experience. You can customize your cookie preferences below. See our {cookiePolicyLink} for more details.

Cookie Settings

Link, Press control-option-right-arrow to exit

Empty Help Center

Uh oh. That page doesn’t exist.

Disappointed

Neutral

Smiley

Thinking...

Searching through sources...

Analyzing...

Tickets submitted through the messenger or by a support agent in your conversation will appear here.

From:
Github (Reviews)	`updated_at`
Gitlab (MRs)	`review_event.created_at`
Bitbucket (PRs)	`pull_request.participants.*.participated_on`
Azure DevOps (PR Threads)	`lastUpdatedDate`
Jira	N/A
ClickUp	N/A
Trello	N/A

Reviews > Updated at

Reporting Use Cases