Post technical updates directly into support threads

When an issue status changes in FogBugz, automatically add a ticket comment in SolarWinds Service Desk to keep support reps informed of engineering progress.

Try:

See all SolarWinds Service Desk + FogBugz 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.

SolarWinds Service Desk Explore SolarWinds Service Desk →

Triggers

New ticket or conversation

Fires when a new support ticket or chat conversation starts in SolarWinds Service Desk.

Ticket status changed

Fires when a ticket's status changes in SolarWinds Service Desk.

Ticket assigned

Fires when a ticket in SolarWinds Service Desk is assigned to an agent.

SLA breached

Fires when a ticket in SolarWinds Service Desk breaches its response SLA.

Actions

Create ticket

Creates a new ticket in SolarWinds Service Desk.

Update ticket status

Updates a ticket's status in SolarWinds Service Desk.

Assign ticket

Assigns a ticket in SolarWinds Service Desk to an agent.

Reply to a ticket or chat

Posts a reply or internal note on a ticket or conversation in SolarWinds Service Desk.

FogBugz Explore FogBugz →

Triggers

New bug report

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

Test run finished

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

Comment added

Fires when someone comments on a bug in FogBugz.

Actions

Create issue

Creates a new bug or issue in FogBugz.

Update issue

Updates the status or details of an issue in FogBugz.

Add comment

Adds a comment to a bug in FogBugz.

Escalate support tickets to software engineering When a new ticket is created in SolarWinds Service Desk, automatically create an issue in FogBugz so developers can investigate the underlying bug. See details

Update support ticket statuses when code deploys When a deployment is tracked in FogBugz, update the ticket status in SolarWinds Service Desk so support teams know the patch has reached production. See details

See all SolarWinds Service Desk + FogBugz integrations → · Browse the full workflow library →

Enterprise-grade security

Visit our Security Center Review the DPA

FAQ

Common questions

Can Knit build “Post technical updates directly into support threads” between SolarWinds Service Desk and FogBugz?

Yes — describe it in the box above and Knit's Integrations Agent researches SolarWinds Service Desk and FogBugz'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.

How does connecting developer tools with ticketing systems help support teams?

Integrating FogBugz with SolarWinds Service Desk bridges support and engineering by escalating user-reported tickets into developer issues and updating tickets when fixes deploy.

Can code deployments automatically update customer tickets?

Yes, when a deployment is tracked in FogBugz, corresponding ticket statuses in SolarWinds Service Desk can automatically update to inform agents that fixes are live.