Reqs for Azure DevOps

See, link and review the requirements behind every work item. Reqs for Azure DevOps connects your organization to Reqs, Ultraist's requirements tool, so requirements live in Reqs, work lives in Azure Boards, and the two stay in step.

Reqs for Azure DevOps needs a Reqs workspace. Don't have one? Sign up for Reqs.

Requirements on every work item

A Reqs group on the work item form shows the requirements a work item delivers: their status, summary and acceptance criteria. Search and link a req in a couple of clicks, and unlink it just as easily.

Know when a requirement changes

When a linked requirement changes in Reqs, the work item flags it with exactly what changed, and gets a comment with the diff so everyone following it hears about it. Mark it reviewed once you've taken it into account.

Delivery that follows Azure Boards

State, assignee, iteration and target date changes flow back to Reqs as they happen, so each Feature in Reqs shows how much of its work is done, in progress and still to do, and when it will land from the sprints its open work is planned into.

Work from Reqs

From Reqs, create work items for requirements (or a parent with an item for each requirement beneath a Feature), link existing work items, and publish spec pages to your project wiki.

Get started

1. In Reqs, go to Settings → Integrations → Azure DevOps and generate a pairing key.
2. In Azure DevOps, open Organization settings → Reqs and enter the key. Then either:
   • Connect with Microsoft Entra (recommended): an Entra administrator consents to the Reqs app. Before finishing, add Reqs for Azure DevOps as a user of the organization (Basic access, with access to the projects Reqs should see) and to Project Collection Administrators, which live updates need. Then select I've done that — finish pairing.
   • Use a personal access token with Work Items, Service Hooks and Wiki (Read & write).
3. Choose the projects open to Reqs, then open a work item and link a requirement.

Full setup and usage: Reqs for Azure DevOps documentation.

Privacy and security

The integration sends Reqs only what it needs about the work items you link: their title, type, state, project, iteration, target date and assignee's name. It never reads descriptions, comments or attachments, and never sends email addresses. Microsoft Entra connections use your own tenant's consent, so we store none of your credentials. See our Privacy Policy and Security pages.

Support

Email support@ultraist.dev or use our contact page. Report security issues to security@ultraist.dev.