Flag failed test runs

When a test run fails in PractiTest, create a high-priority task in Teamwork.

Try:

See all PractiTest + Teamwork integrations or talk to a human

Trusted by teams already building on Knit·

4.9/5 on G2·

Google for Startups Accelerator

How Knit builds this workflow

The Agent researches both APIs and wires the trigger on one side to the action on the other — no pre-built connector required. Here is the vocabulary it has to work with.

PractiTest Explore PractiTest →

Triggers

New bug report

Fires when a new bug or issue is reported in PractiTest.

Test run finished

Fires when a test run or build passes or fails in PractiTest.

Comment added

Fires when someone comments on a bug in PractiTest.

Actions

Create issue

Creates a new bug or issue in PractiTest.

Update issue

Updates the status or details of an issue in PractiTest.

Add comment

Adds a comment to a bug in PractiTest.

Teamwork Explore Teamwork →

Triggers

New task created

Fires when a new task, job or item is created in Teamwork.

Task completed

Fires when a task in Teamwork is marked complete.

Due date approaching

Fires when a task's due date in Teamwork is coming up.

Status changed

Fires when a task, job or project changes status in Teamwork.

Actions

Create task

Creates a new task, job or item in Teamwork.

Update task

Updates a task's status or assignee in Teamwork.

Add comment

Posts a comment on a task in Teamwork.

Assign task

Assigns a task in Teamwork to a team member.

Create tasks from new bugs When a new bug is reported in PractiTest, create a task in Teamwork. See details

Update bugs when tasks close When a task is completed in Teamwork, update the matching issue in PractiTest. See details

See all PractiTest + Teamwork integrations → · Browse the full workflow library →

Enterprise-grade security

Visit our Security Center Review the DPA

FAQ

Common questions

Can Knit build “Flag failed test runs” between PractiTest and Teamwork?

Yes — describe it in the box above and Knit's Integrations Agent researches PractiTest and Teamwork's public API docs (or your own uploaded docs) and builds a working workflow, whether or not either app already has a pre-built connector.

How long does it take to build?

Minutes to a first working version, not weeks — you test it against real data before it goes anywhere near production.

Why connect a bug tracker to a project management tool?

Testers work in PractiTest, but the team plans in Teamwork. Syncing bugs between them means fixes are prioritized with the rest of the work.

Can completed tasks mark bugs as fixed?

Yes. When a task is completed in Teamwork, you can update the linked bug in PractiTest so testers know to verify it.