Dataset: Activity Events
Entity: Activity Events
Field ID: src_workflow_status
Type: Text
Description: The workflow status that the WORKFLOW_STATUS_UPDATED event transitioned from. NULL for the first transition 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:
This field is calculated by looking at the workflow status of the
WORKFLOW_STATUS_UPDATEDevent preceding the event.
From: |
|
Github (Timeline Items) | Calculated |
Gitlab (Discussions, State Events) | N/A |
Bitbucket (Activity) | N/A |
Azure DevOps (PR Threads) | N/A |
Jira (Changelog, Worklog) | Calculated |
ClickUp (Issue timestamps) | N/A |
Trello (Actions) | Calculated |
Reporting Use Cases
The Source Workflow Status field is a powerful attribute within the Activity Events dataset that captures the "from" state for any WORKFLOW_STATUS_UPDATED event. It is the key to understanding how work flows through your process, enabling you to build Sankey-like diagrams, analyze process churn, and pinpoint workflow bottlenecks.
Analyzing Workflow Transitions: This field's primary use, in combination with the workflow_status field (the "to" state), is to analyze the flow between statuses.
To see a complete picture of all your workflow transitions, you can create a list report with
Source Workflow StatusandWorkflow Statusas dimensions and aCOUNT()metric. This will show you exactly how many times issues have moved from "To Do" to "In Progress," from "In Progress" back to "To Do," and so on.
Building Historical Cumulative Flow Diagrams: This field is essential for accurately reconstructing the number of items in a particular status at any point in the past.
To build a chart showing the historical count of items in the "In Progress" status, you need to count the items that entered and 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.
Filtering for Process Inefficiencies: You can create reports to find issues that are moving backward in your workflow, which is a strong indicator of rework or unclear requirements.
For example, you can find all instances where an issue was moved out of "In Progress" and back into "To Do" by using a filter where
Source Workflow Status = "In Progress" and Workflow Status = "To Do".