Dataset: Activity Events
Entity: Activity Events
Field ID: workflow_status
Type: Text
Description: The workflow status associated with the WORKFLOW_STATUS_UPDATED event. NULL for any other event action.
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) | N/A |
Gitlab (Discussions, State Events) | N/A |
Bitbucket (Activity) | N/A |
Azure DevOps (PR Threads) | N/A |
Jira (Changelog, Worklog) |
|
ClickUp (Issue timestamps) | N/A |
Trello (Actions) |
|
Reporting Use Cases
The Workflow Status field from the Activity Events dataset captures the "to" state for any WORKFLOW_STATUS_UPDATED event, making it the counterpart to Src Workflow Status. It is essential for analyzing the direction of your workflow, building cumulative flow diagrams, and understanding which stages of your process are most active.
Filtering for Inbound Activity: You can create reports that focus on all the work that has moved into a specific stage.
To see all the items that entered your "In Review" column last week, you can create a report with a filter where
Workflow Status = "In Review" and Created At in the previous 7 days.
Analyzing Workflow Destinations: When used as a dimension, this field shows you the most common destination points in your workflow.
A bar chart with
Workflow Statusas a dimension andCOUNT()as a metric will show which of your workflow columns receive the most inbound traffic, helping you identify the most active stages of your process.
Building Historical Cumulative Flow Diagrams: This is the field's most powerful use case, enabling you to reconstruct the state of your workflow at any point in the past. By tracking what enters a state versus what leaves it, you can calculate a running total.
To build a chart showing the historical count of items in an "In Progress" state, you need to count the items that entered and subtract the items that left. A custom formula like
SUM_CUMULATIVE(IF(workflow_status == "In Progress", 1, 0)) - SUM_CUMULATIVE(IF(src_workflow_status == "In Progress", 1, 0))will give you a running total of items in that state over time.