Dataset: Activity Events
Entity: Activity Events
Field ID: id
Type: Text
Description: The ID assigned to the record by the source app using the event ID (when applicable) or a composite ID based on unique event attributes. Unique across all records from the same app.
Source: App
Transformation logic: N/A
From: |
|
Github (Timeline Items) |
|
Gitlab (Discussions, State Events) | Discussions: State Events: |
Bitbucket (Activity) | Hexdigest generated from the event content (Bitbucket events do not have native IDs) |
Azure DevOps (PR Thread) | Generated from the thread |
Jira (Changelog, Worklog) | Changelog: |
ClickUp (Issue timestamps) |
|
Trello (Actions) |
|
Reporting Use Cases
The ID (Source) field from the Activity Events dataset provides the unique identifier for an event as it appears in the source application (e.g., the ID of a Jira history item). Its primary role in reporting is to provide a direct reference for auditing and to ensure that each event can be uniquely identified in detailed lists and drilldowns.
Context in Drilldowns and Audits: When you create a high-level report, such as a chart of "Issues Closed per Day," and you drill down to see the individual events, including the
ID (Source)in the drilldown list provides a unique, traceable identifier for each specific action. This allows for precise auditing and cross-referencing with the source tool's activity log.Filtering for Specific Events: While a less common use case, if you know the exact ID of a specific event from the source application's API or logs, you can use a direct filter to isolate it for investigation.
For example, you could create a report with a filter like
ID (Source) = "12345678"to pull up the details of a single, specific event.