Explore

Straddle 101 - Internal

Workflows

tl;dr

We're setting up specific workflow statuses in Linear to streamline task management and project tracking.

The PRD integrates links to Linear's documentation for detailed guidance, ensuring clarity and easy access to information for the team.

Narrative

The transition to Linear's workflow management is a strategic shift towards a more organized and transparent project tracking system.

By adopting Linear's workflows, we aim to resolve existing visibility issues, ensuring that the progress and scope of each task are clearly outlined and accessible, facilitating more effective planning and execution.

Problem

Our current challenge is the lack of visibility regarding the progress and scope of work. This results in difficulty in tracking project milestones, understanding current task status, and planning future work efficiently.

Solution

Implementing Linear's workflow management system will enable us to establish a structured, efficient process for task progression and status tracking. This system will provide the necessary visibility by clearly defining each stage of a task within our project lifecycle.

By utilizing Linear's interface and detailed tracking features, we will gain immediate visibility into each task's current status, identify any delays in real-time, and ensure smooth progression of work through predefined stages.

What’s a workflow?

As you work on and complete issues, they'll move through workflows. These are the statuses that you'll see group issues on list views and show up as column headers on boards. We create a default workflow for you that you can further customize to have more statuses, different names, and colors.

You can update issue statuses manually, but we recommend enabling our smart automations that keep issues up to date and save you the time and hassle of "managing tickets."

The GitHub integrations move issues to In Progress when you copy the git branch name and continues to update the status as the PR is drafted, opened, reviewed, and merged. Cycle automations move issues to and from the backlog and you can set issues to close and archive on their own so lists stay relevant.

Technical Specifications

Key Workflow Features

Default Status: The initial status for new issues is 'Backlog'. More on this can be found in the

Default Status section⁠

of the Linear documentation.

Triage: An additional status acting as an inbox for the team, useful for managing incoming tasks. Detailed information is available in the

Triage section⁠

of Linear's documentation.

Auto-close and Auto-archive: Features for automatically managing inactive or completed issues. Further details are in the

Auto-close and Auto-archive section⁠

Duplicate Issue Status: When an issue is marked as a duplicate, it changes to 'Canceled', but you can create a custom 'Duplicate' status. Explore this in the

Duplicate Issue Status section⁠

Standard Statuses 2