Resolve issue reports when project tasks complete
When a task is marked complete in Teamwork, automatically resolve the corresponding issue in Azure DevOps to maintain clean issue trackers.
See all Azure DevOps + Teamwork integrations or talk to a human
Google for Startups AcceleratorHow 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.
Azure DevOps Explore Azure DevOps →
TriggersFires when a job, build or file conversion finishes in Azure DevOps.
Fires when a job, build or API request fails in Azure DevOps.
Calls an Azure DevOps endpoint with data from an earlier step.
Creates a PDF, image or converted file with Azure DevOps.
Checks or enriches a phone number, address or IP with Azure DevOps.
Teamwork Explore Teamwork →
TriggersFires when a new task, job or item is created in Teamwork.
Fires when a task in Teamwork is marked complete.
Fires when a task's due date in Teamwork is coming up.
Fires when a task, job or project changes status in Teamwork.
Creates a new task, job or item in Teamwork.
Updates a task's status or assignee in Teamwork.
Posts a comment on a task in Teamwork.
Assigns a task in Teamwork to a team member.
More Azure DevOps + Teamwork workflows
See all Azure DevOps + Teamwork integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “Resolve issue reports when project tasks complete” between Azure DevOps and Teamwork?
Yes — describe it in the box above and Knit's Integrations Agent researches Azure DevOps 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.
What's the most common Developer Tools + Project Management automation?
Marking the linked task in Teamwork complete (or moving it to review) automatically when a pull request merges in Azure DevOps.
Does this need commit messages to reference the task ID?
That's the most reliable way to match them, though the Agent can also match on branch name or a manually linked reference depending on your workflow.