Dataset: Comments
Entity: Comments
Field ID: updated_at
Type: Datetime
Description: The datetime at which the comment was last updated.
Source: App
Transformation logic: N/A
| From: | 
 | 
| Github (Comments) | 
 | 
| Gitlab (Comments) | 
 | 
| Bitbucket (Comments) | 
 | 
| Azure DevOps (Comments) | 
 | 
| JIRA (Comments) | 
 | 
| ClickUp (Comments) | 
 | 
| Trello (Comments) | 
 | 
Reporting Use Cases
The Updated At field from the Comments dataset is a specialized timestamp that captures the moment a comment was last edited. Its primary use is for auditing and tracking changes in communication, helping you identify when and how discussions have evolved over time.
- Filtering for Edited Comments: The most direct use of this field is to find comments that have been modified after their initial creation. - You can create a report highlighting edited comments by using a custom formula such as - updated_at > created_at. This is useful for auditing purposes or for reviewing discussions where the original context may have changed.
- You can also focus on recently edited comments to see the latest changes in a discussion, using a filter like - Updated At in the previous 24 hours.
 
- Analyzing Comment Evolution: By comparing the - Updated Atand- Created Attimestamps, you can measure the "time to correction" or how long it takes for comments to be revised.- In a list report of edited comments, you can add a custom dimension with the formula - (updated_at - created_at) / HOUR()to show how many hours passed before the comment was changed. A long duration might indicate that the initial comment was left for a while before being corrected.
 
- Tracking Recent Activity: Since a comment edit is a form of activity, you can use this field to find recently active discussions, although the - Updated Atfield on the parent issue or pull request is often a more holistic measure for this purpose.

