Workflows

A workflow is the set of states a test case, a test run, or an exploration moves through — Draft to In review to Approved, Not started to In progress to Complete. Each of the three has its own independent workflow, its own default state, and its own automation. They are configured in Settings → Workflows.

This module used to be called Lifecycles. The name changed; nothing else about it moved. The old address, /docs/lifecycles, still resolves here, and the settings page itself is still at /admin/lifecycles — bookmarks and saved links keep working.

What a workflow state is

A workflow state is a label that says where an item currently stands. States answer questions like:

• Which test cases have been reviewed and approved?
• Is this run still being executed, or is it done?
• Which explorations have been wrapped up?

You define the states that suit your team — the name, an icon and a colour, the order they appear in, and which projects offer them. Nothing is hardcoded.

Three workflows, on three tabs

The page opens on three tabs, and each one is a separate workflow. A state belongs to exactly one of them; nothing is shared across the three. The tab you are on is part of the address, so a link to a particular workflow lands on it.

Test case workflow

The State property on a test case, its column in the case list, and the State grouping and filter. Example states: Draft, In review, Approved.

Test run workflow

The State row on a run’s About card, the run list’s State facet, and the state chip in the run header. Example states: Not started, In progress, Complete. Two automation rules can move a run between them on their own.

Exploration workflow

The state a new exploration starts in, and the state it moves to when it is closed. Note that no exploration screen shows or lets you change this state today — it is applied on the server and is not the same thing as the built-in Planned → Live → Debriefed session state you see on the exploration itself.

What the page looks like

Under the tabs sits one panel listing that workflow’s states, with a search box, a refresh button and New state. Each row carries:

• State — the icon in its colour, the name (a link to the state’s own page), and a Default chip on whichever state is the default.
• Order — the display order number the list is sorted by.
• Projects — All, a count, or a None warning.
• Status — Enabled or Disabled.
• A ··· menu holding every action for that row.

Below the list is an automation panel for the same workflow — on the same page, not behind a button. See Workflow Automation.

Getting started

1. Go to Settings → Workflows.
2. Pick the tab you want to configure: Test case workflow, Test run workflow, or Exploration workflow.
3. Click New state and fill in the editor that opens. See Workflow States.
4. Decide which projects offer it — see Project Assignment.
5. Set the automation for that workflow in the panel under the list.

Who can manage workflows

Workflows is a workspace-level setting: it is configured once and applies everywhere, and it is not gated by your plan.