Frequently asked questions

Vindex catches the five things that make requirements fail in sprint — vague scope, missing acceptance criteria, stories too big to estimate, hidden dependencies, and untestable outcomes. Scoring is based on INVEST, the industry-standard checklist for user story quality, but you don't need to know the framework to get value from the results.

No. Vindex evaluates tickets in the tools you already use — Jira, Azure DevOps, Asana, Trello, Monday — and surfaces story health scores back in those tools. It's not a replacement for refinement either; it's the signal that tells you which stories need refining.

No. Vindex gives you structured, plain-English recommendations for how a story could be improved. A human still writes the story. That's deliberate — refinement is a conversation, and Vindex is there to make the conversation sharper.

A number between 0 and 10 that summarises how ready a story is for sprint planning. It's the arithmetic mean of the six INVEST dimension scores and is shown rounded to one decimal place (for example 6.4). The default quality gate is 7.0 — below that, a story shouldn't enter a sprint without refinement.

7.0 and above is healthy. 5.0 to 6.9 needs review - surface it in refinement. Below 5.0 is at risk and should not go into a sprint. See Interpreting scores for the full breakdown.

Dimension scores are integers from 1 to 10. Below 5 sits in the bottom 40% of the scale and is a clear signal the story doesn't satisfy that dimension well enough to move forward. On the results page — and in the API's dimension_fail_counts — that threshold is what powers headlines like “31 of your 48 stories are missing testable acceptance criteria.”

The default gate is 7.0, but company admins can tune it to match their own definition of ready. If you need per-project gates or team-specific thresholds, contact us — that's on the roadmap.

Jira Cloud, Azure DevOps, Asana and Trello are supported today. Monday is on the roadmap.

Yes, for the initial install. Forge apps require a site administrator. Once installed, the app works for every user in your instance without further admin involvement.

The public /evaluate flow scores the first 5 tickets in your CSV so you can see what Vindex finds before signing up. Full-backlog scoring is available once you connect an integration or register an account.

Scores are stored in a Vindex Data Platform. CSV uploads from the public flow are retained for 24 hours and then deleted automatically by a TTL index — no CSV contents are written to the filesystem.

No. Scores are scoped to your customer_id, which is resolved to your company at query time. Portal endpoints return 404 Not Found for any score that belongs to a different company — we never reveal records across company boundaries.

No. Vindex records the model and provider used for every scoring run, but model_metadata.temperature is always excluded from API responses and callback payloads.