How is Vantage different from ChatGPT or Claude?

ChatGPT and Claude write you a document. Vantage keeps the document, prototype, tickets and roadmap connected to the feedback and decisions behind them, and tells you when one of them changes. You can also bring your Vantage context into Claude or ChatGPT, so you don’t have to choose.

Do I have to move off Notion or Linear?

No. Keep the tools you use and connect them to Vantage. Tickets push to Linear with two-way sync, and you approve every change that comes back.

What can I do in the first ten minutes?

Paste customer feedback or describe a problem, and get a PRD with every requirement linked to its source. You can try the demo on this page without signing up. Connect your tools whenever you’re ready.

I own several projects. What does Vantage do across them?

It briefs you every morning on what needs your call, catches specs that contradict each other, and flags anything that went stale after a decision changed. It works for a single project and earns its keep at two or more.

What if the AI gets something wrong?

Nothing updates silently. Every requirement cites the quote, call or metric behind it, and every change arrives as a diff you accept or reject before it touches your docs, tickets or Linear.

Can I use Vantage from Claude or ChatGPT?

Yes. Connect Vantage’s MCP server to Claude, add the GPT Action in ChatGPT, or use an API key. Then ask about your projects, search your specs, or create tickets from wherever you work.

Start on your own for free. When teammates join, they work from the same context, with admin, editor and viewer roles and private drafts that stay invite-only until you publish.

What does fair use mean on the unlimited features?

Unlimited features are meant for real day-to-day work by one person: up to 50 questions a day on Pro and Business, and on Business up to 10 PRDs, journeys or ticket batches a day. Very few people get close. If your team regularly needs more, talk to us.

Your data is encrypted in transit, and we never train on it. The AI providers we use are contractually barred from training on it too. You can disconnect any integration or delete your account at any time. We’re pursuing SOC 2 Type II.

How much does it cost?

Vantage is free to start with 300 credits and no credit card. Projects are unlimited on every plan, and AI work like generating a PRD or a ticket batch uses credits. Pro is $19 per seat a month billed annually ($25 monthly) with 1,500 credits a month, unlimited questions and prototypes. Business adds a shared team workspace and 4,000 credits per seat a month.

Can a bug have different affected and fix versions?

Yes. The affected values describe where the bug occurs; the Fix version describes intended delivery. For example, a bug in 3.6.1 can be planned for a fix in 3.6.2.

Why does adding an Affects version not add the issue to that release?

Release membership uses Fix versions. Affects versions supports finding issues impacting a product version without claiming those issues ship their fix in that version.

What if a bug was not tested on every older version?

Record the versions supported by reproduction evidence and note the uncertainty in the issue. Ask for additional testing when the impact decision depends on other versions.

How-To2026-10-263 min read

Map Jira Fix Versions and Affects Versions

Use Fix versions for the release intended to deliver a change and Affects versions for product versions where a problem occurs. This guide corrects those issue fields; creating and releasing versions is a separate workflow.

Step-by-step guide

Check field access

Open a representative bug in the intended project. Check that you can edit its version fields and that the required version values already exist for that project.

Separate observed and planned versions

Read the bug report and identify the observed affected versions separately from the intended fix delivery. Ask the reporter or release owner when the source evidence is ambiguous.

Set Affects versions from evidence

In the issue details, select the versions where the bug was actually observed in Affects versions. Do not infer every older version is affected.

Worked example: A bug reproduced in 3.6.0 and 3.6.1 is planned for correction in 3.6.2. Record 3.6.0 and 3.6.1 as affected, with 3.6.2 as the Fix version.

Correct the Fix versions value

Open Fix versions in the issue details and choose the approved delivery version. If the field is hidden, use Show more; ask an administrator to check the screen configuration if it remains unavailable.

Preserve history when rescheduling

If the fix moves to a later release, update the planned Fix version and record the scope decision in the issue. Preserve the observed Affects versions rather than moving both fields together.

Review release-filter effects

Check the release view or saved Fix-version filter and confirm the bug is assigned to the intended delivery set. Affects versions supports investigation of impacted versions; it does not add the bug to a release.

Verify the corrected issue

Compare both fields with the reproduction evidence and delivery decision. Ask the owner to confirm the mapping before correcting a larger set of bugs.

Common mistakes

Using the discovery version as the delivery target

The version where a bug is found can differ from the release that will deliver its fix. Enter each value in the field that represents its meaning.

Changing affected versions when a fix slips

A delivery delay changes the target Fix version, not the historical evidence of versions where the bug was observed.

Sources and verification

Based on product documentation checked on 2026-10-24. This is a documentation-based guide, not a hands-on benchmark. Features and availability can change.