Issues & support
Set up Azure DevOps
Connect Azure DevOps to make work items and project wikis searchable — each work item (bug, user story, task and so on) becomes a document with its description, repro steps and comment thread, tied to its project, state, assignee and tags, and each wiki page a document of its own, so “how did we fix that bug” answers from the closed item and “what's the deploy runbook” from the wiki. Read-only.
Before you start
- The credential is a personal access token: in Azure DevOps click the user-settings icon (top right) → Personal access tokens → New Token.
- Give it READ on Work Items and Wiki — nothing else is used — pick a sensible expiry, and copy it right away; it's shown once. Only reads are ever issued.
- Documents → Azure DevOps, enter Organization — the acme in dev.azure.com/acme; pasting the full address is fine, the name is picked out of it — and paste the Personal access token.
- Projects: optional project names exactly as Azure DevOps shows them, one per line — blank syncs every project the token can read.
- Choose access groups, Test, then Sync.
What comes in
- Each work item becomes a document titled project #id: title — type, state, author, assignee, tags and last-changed date, the description, a Repro steps section where the item has one, and the whole comment thread, each comment with who wrote it and when. Done, closed, resolved and removed items come in as history, not just open ones.
- Each page of each project wiki becomes a document of its own, titled with the project and the page's name and noting its path in the wiki.
- A new comment on an otherwise untouched work item is picked up on the next sync. Code, pipelines and pull requests are not read.
Access
Access is allow-only: the groups chosen on the source cover everything Azure DevOps brings in — the source exposes no per-item viewers to mirror, so Azure DevOps' own work-item and wiki permissions are not reflected here.
Caps: 50 projects, the 1,500 most recently changed work items per project, 2,000 comments per work item and 300 pages per wiki — Sync notes each cap it hits, and items or pages that slide out of those windows stay searchable rather than disappearing. A personal access token expires on the schedule chosen when it was created; from then on Test and Sync report it as expired or revoked until you paste a fresh one here. A project the token can't read is skipped and noted rather than failing the whole sync, its existing documents kept; a project with no wiki simply contributes no pages. Test says how many projects it reached and names the first of them. Revoke access any time by deleting the token under Personal access tokens in Azure DevOps.
Last updated 20 Sep 2026