TriggerHold — Schedule Work Item Follow-up

Schedule a future follow-up on any work item, right from the work item form — no relay backend, no separate app to configure per project.

What it does

• Adds a TriggerHold panel to the work item form. Pick a date/time (and, if your admin's template allows it, a State), click Schedule with TriggerHold, and you're done.
• At the scheduled time, TriggerHold calls the Azure DevOps REST API directly — either creates a new, linked follow-up work item (the original is left untouched) or updates the original work item in place, depending on the admin-configured template for that Project/Area Path.
• Everyone viewing the work item sees the pending follow-up, with Edit and Cancel schedule actions. Once it fires, the panel shows what happened instead.
• Scheduling and cancelling post a comment on the work item's Discussion so there's a visible audit trail.

Setup

An org admin configures TriggerHold once, org-wide, from Organization Settings → TriggerHold: a TriggerHold API key, the name of a stored secret holding an Azure DevOps Personal Access Token, and any number of callback templates that control what happens (create vs. update, State, title prefix, which fields carry over) per Project and Area Path.

Requires a TriggerHold account.

Learn more

See triggerhold.io and the Azure DevOps examples page for the full "no backend required" recipe this extension implements.