Dataset: Activity Events
Entity: Activity Events
Field ID: action
Type: Text
Description: The type of action described by the event. Possible values are:
CREATEDthe issue/PR was createdCLOSEDthe issue/PR was closedREOPENEDthe issue/PR was opened was being closedMERGEDthe PR was mergedREVIEWER_ASSIGNEDa reviewer was assigned (requested reviewers) to the PR. Keypup generates one event per assigned reviewer in case of bulk assignments.REVIEWER_UNASSIGNEDa reviewer was unassigned (requested reviewers) from the PR. Keypup generates one event per unassigned reviewer in case of bulk unassignments.USER_ASSIGNEDa user was assigned (assignees) to the issue/PR. Keypup generates one event per assigned user in case of bulk assignments.USER_UNASSIGNEDa user was unassigned (assignees) from the issue/PR. Keypup generates one event per unassigned user in case of bulk unassignments.WORK_LOGGEDa user logged some time on the issue/PR.WORKFLOW_STATUS_UPDATEDthe issue transitioned to a new workflow status.
Source: Applications support the following events
Github:
CREATED,CLOSED,REOPENED,MERGED,REVIEWER_ASSIGNED,REVIEWER_UNASSIGNED,USER_ASSIGNED,USER_UNASSIGNEDGitLab:
CREATED,CLOSED,REOPENED,MERGED,REVIEWER_ASSIGNED,REVIEWER_UNASSIGNED,USER_ASSIGNED,USER_UNASSIGNED,WORK_LOGGEDBitbucket:
CREATED,CLOSED,MERGED,REVIEWER_ASSIGNED,REVIEWER_UNASSIGNEDAzure DevOps:
CREATED,CLOSED,MERGED,REVIEWER_ASSIGNED,REVIEWER_UNASSIGNEDJira:
CREATED,CLOSED,REOPENED,USER_ASSIGNED,USER_UNASSIGNED,WORK_LOGGED,WORKFLOW_STATUS_UPDATEDClickUp:
CREATED,CLOSED. ClickUp does not expose an events API. Keypup generates these two events based on the issue timestamps (date_created&date_closed)Trello:
CREATED,CLOSED,REOPENED,USER_ASSIGNED,USER_UNASSIGNED,WORKFLOW_STATUS_UPDATED
Transformation logic: N/A
From: |
|
Github (Timeline Items) |
|
Gitlab (Discussions, State Events) | Based on |
Bitbucket (Activity) | Based on |
Azure DevOps (PR Threads) | Based on the thread |
JIRA (Changelog, Worklog) | Changelog: based on field changes Worklog: |
ClickUp (Issue timestamps) |
|
Trello (Actions) |
|
Reporting Use Cases
The Action field is the core attribute of the Activity Events dataset, as it defines the type of event that occurred. It is essential for creating historical trend reports, such as cumulative flow diagrams, and for analyzing the volume and sequence of different activities over time.
Filtering for Specific Activities: You can create highly focused reports by filtering on one or more event types.
Track New vs. Completed Work: To analyze throughput, you can compare the number of
CREATEDandREOPENEDevents against the number ofCLOSEDandMERGEDevents in a given period.Monitor Workflow Changes: To see how often issues are moved between statuses, you can create a report filtered where
Action = "WORKFLOW_STATUS_UPDATED".Analyze Assignment Activity: To understand how frequently work is assigned or reassigned, you can filter where
Action equals any of "USER_ASSIGNED", "USER_UNASSIGNED".
Reporting on Activity Distribution: Using action as a dimension provides an overview of your team's activities.
A pie chart with
Actionas the dimension andCOUNT()as the metric can quickly show you the most common types of events, revealing whether your team spends more time creating, closing, or updating items.
Custom Formulas for Historical Trend Analysis: This is the most powerful use of the Activity Events dataset. By using cumulative formulas, you can reconstruct the state of your backlog at any point in the past.
Historical "Open Items" Count: You can create a line chart showing the number of open items over time. Use a time-based dimension (e.g.,
YEAR_MONTH(created_at)) and a custom metric likeSUM_CUMULATIVE(IF(CONTAINS(["CREATED", "REOPENED"], action), 1, -1)). This formula adds 1 for every item created or reopened and subtracts 1 for every item closed or merged, giving you a running total of open items at any point in history.