Skip to main content

Issues and PRs > Workflow Status

Tom Williams avatar
Written by Tom Williams
Updated over a week ago

Dataset: Issues & Pull Requests

Entity: Issues

Field ID: workflow_status

Type: Text

Description: The team-defined status of the issue, as seen in the source project management application.

Source: App

Transformation logic: N/A

From:

Github (PRs, Issues)

Repositories: N/A
​Projects: mapped from Status

Gitlab (PRs, Issues)

N/A

Bitbucket (PRs)

N/A

Azure DevOps (PRs, Issues)

N/A

JIRA (Issues)

Use status.id on issues to retrieve the Status object then map Status.name

ClickUp (Issues)

Use status_id on issues to retrieve the Status object then map Status.status

Trello (Issues)

Use idList to retrieve the BoardList object then map BoardList.name

Reporting Use Cases

The Workflow Status field is the primary attribute for tracking an issue's real-time progress through your team's defined development process (e.g., the columns on your Jira or Trello board). It is essential for building Kanban-style boards, identifying bottlenecks, and analyzing your workflow's efficiency.

  • Filtering for Workflow Management: The most common use of this field is to filter items based on their current stage, which is the foundation for building any process-oriented board or report.

    • Kanban Boards: You can create columns for each stage of your process, such as a "Work in Progress" column filtered where Workflow Status = "In Progress", or a "QA" column filtered where Workflow Status = "In QA".

    • Find Blocked Work: Create a high-priority list of all items that are currently blocked by using a filter like Workflow Status = "Blocked".

  • Reporting on Pipeline Health: Using workflow_status as a dimension provides an instant snapshot of your entire development pipeline.

    • A bar chart with Workflow Status as the dimension and COUNT() as the metric will show you exactly how many issues are in each stage. A large number of items piling up in one status is a clear sign of a bottleneck.

  • Calculating Time in Status: While this field shows the current status, its real power is unlocked when used with the workflow_timeline field to analyze how long items spend in each stage.

    • You can measure the average time issues spend in the review phase with a custom formula metric like AVG(TIMELINE_DURATION(workflow_timeline, "In Review")) / DAY(). Tracking this over time can show if your review process is getting faster or slower.

Did this answer your question?