Flag failed test runs

When a test run fails in Sifter, create a high-priority task in Jira Software Server.

Try:

See all Jira Software Server + Sifter 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.

Jira Software Server Explore Jira Software Server →

Triggers

New task created

Fires when a new task, job or item is created in Jira Software Server.

Task completed

Fires when a task in Jira Software Server is marked complete.

Due date approaching

Fires when a task's due date in Jira Software Server is coming up.

Status changed

Fires when a task, job or project changes status in Jira Software Server.

Actions

Create task

Creates a new task, job or item in Jira Software Server.

Update task

Updates a task's status or assignee in Jira Software Server.

Add comment

Posts a comment on a task in Jira Software Server.

Assign task

Assigns a task in Jira Software Server to a team member.

Sifter Explore Sifter →

Triggers

New bug report

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

Test run finished

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

Comment added

Fires when someone comments on a bug in Sifter.

Actions

Create issue

Creates a new bug or issue in Sifter.

Update issue

Updates the status or details of an issue in Sifter.

Add comment

Adds a comment to a bug in Sifter.

Create tasks from new bugs When a new bug is reported in Sifter, create a task in Jira Software Server. See details

Update bugs when tasks close When a task is completed in Jira Software Server, update the matching issue in Sifter. See details

See all Jira Software Server + Sifter 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 Jira Software Server and Sifter?

Yes — describe it in the box above and Knit's Integrations Agent researches Jira Software Server and Sifter'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 Sifter, but the team plans in Jira Software Server. 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 Jira Software Server, you can update the linked bug in Sifter so testers know to verify it.