Test Management Workflows for Jira Teams

Sherlock. helps product and QA teams turn Jira context into repeatable test coverage and release execution. Choose the team structure or testing challenge closest to your workflow.

PAY · Payments Platform / Release 4.2
One request, whatever the team
AK Cover the refund flow for 4.2, including permissions.
PAY-1841 Refund policy refund-api.yaml
S Brief ready: 3 product flows, 2 risks. Review before I create cases.
One workflow, whatever the entry point
TC-104Full refund to original methodApproved
TC-106Refund blocked without finance roleP2
Release run · Fix Version 4.2
In scope
28
Executed
24
Pass rate
86% +4
Defects
3

Find your workflow

Find the Right Sherlock. Workflow

Three describe a team structure, three describe a testing problem. They end in the same place.

Use case 01

Release Regression Testing at Halden Pay

Today
The regression pack is chosen from memory, so it is either too wide to finish or too narrow to trust.
With Sherlock
Compare the current Fix Version with the approved baseline and review a focused test run.
Learn more

Use case 02

Embedded QA Teams

Today
Cases live in a separate tool, so release scope and results are reconciled against Jira by hand, every time.
With Sherlock
Manage cases, scope, assignments, execution, defects, and reports in the Jira project.
Learn more

The shared path

One Workflow From Requirements to Release Results

Every use case above enters at the same stage and leaves at the same one. What differs is the request the team starts with.

Product team

“We have no test cases for the refund flow. Start from the epic.”

Embedded QA

“PAY-1902 changed. Which of our approved cases does that affect?”

QA lead

“Build the 4.2 regression scope from what actually changed.”

All three arrive at stage 01.

01

Add context

Select the Jira issues, Confluence pages, files, and release the request depends on.

02

Approve the brief

Confirm the product flows, risks, and approach before any case exists.

03

Review the baseline

Refine the generated cases through the chat and approve them as a version.

04

Prepare and execute the run

Build the scope from the Fix Version, assign it, and record Pass, Fail, or Blocked.

05

Update coverage

Publish the report, link the defects, and approve the updates the run produced.

Start from the requirements you already have, and keep the coverage they produce current as the product moves.