Built for Salesforce Teams

Stop manually checking 
Salesforce after 
every sprint. 

TrueStory reads your Jira acceptance criteria and automatically verifies your Salesforce org matches the spec. Every field, every validation rule, every time. Free to start. Pro for teams that move fast.

Get Started FreeSee How It Works
Works with
Jira Cloud
+
Salesforce
TrueStory
ProPROJ-142
All 4 requirements verified
Story is ready for release
PASSDiscount_Percent__c field exists on OpportunityDiscount_Percent__c
PASSDeal_Desk_Status__c picklist includes Pending, Approved, RejectedDeal_Desk_Status__c
PASSWhen Discount exceeds 30%, save is blocked without approvalDiscount_Approval
PASSApproval_Notes__c visible on Opportunity page layoutApproval_Notes__c
All deal desk approval controls verified against live org metadata. Discount threshold, approval workflow, and page layout confirmed.
Story Readiness0%
✓ Ship it4/4 requirements · 8/8 checks
Post to JiraAdd to RegressionExport
0%
Detection accuracy
Component & constraint
0
Misleading failures
Zero false alarms by design
0
Constraint types
Required to formula
< 0s
Per verification
Metadata + behavioral
The Problem

Your team writes acceptance criteria.
Nobody checks if Salesforce actually matches.

Every sprint ends the same way: manual clicks through page layouts, eyeballing picklist values, hoping validation rules still work.

Silent drift

A developer removes a validation rule. The spec silently drifts. No alert, no audit trail, no one notices until production.

Hours of manual QA

Clicking through page layouts, checking picklist values one by one, across every sandbox. Every. Single. Sprint.

No traceability

No link between the Jira story and the actual Salesforce metadata delivered. Audit asks, you scramble.

The TrueStory Solution

Automated verification.
From Jira to Salesforce.

Parses each AC line and detects constraint types automatically
Resolves field labels to API names against your live org
Runs deterministic checks via Tooling API, not AI guessing
Creates test records to prove validation rules actually fire
Produces an auditable verification trail per requirement
TrueStory
ProPROJ-142
3 of 5 need attention
2 requirements failing, 1 partial
PASSLead_Score__c field exists on LeadLead_Score__c
PASSQualification_Status__c includes MQL, SQL, DisqualifiedQualification_Status__c
FAILWhen Status is SQL, Contact Email is requiredEmail_Required
FAILLead auto-converts when Score exceeds 85Auto_Convert
PARTIALSDR_Notes__c visible on Lead page layoutSDR_Notes__c
Email validation rule not enforced when Status is SQL. Auto-convert automation missing for scores above 85. SDR Notes field partially visible.
Story Readiness0%
⚠ Review2/5 requirements · 10/10 checks
Post to JiraAdd to RegressionExport
Capabilities

Everything you need for
release verification

From parsing acceptance criteria to running live behavioral tests, TrueStory covers the entire verification lifecycle.

Fully Deterministic

Every check is reproducible. No LLM, no hallucinations. Same input always produces the same result. Built for compliance-grade reliability.

Auto-Parse from Jira

Reads your Jira story descriptions natively. Extracts each requirement and identifies the Salesforce components referenced. Labels and API names both work.

Behavioral Testing

Goes beyond metadata. Creates test records with invalid data and confirms your validation rules actually fire. Catches inactive rules and formula errors.

Real Metadata Checks

Verifies fields exist, types match, required flags are set, and page layouts include the right fields. Straight from the Salesforce Tooling API.

19 Constraint Types

Covers required, conditional required, picklist, formula, validation, layout, security, auto-populate, negative value, and more. All detected from natural language AC.

Readiness Scoring

Every story gets a verification gauge showing exactly how ready it is for release. Instant visual signal of what passed, what failed, and what needs attention.

Sprint Dashboard

Track verification coverage across your entire sprint. See which stories are verified, failing, or untested. Detects active sprints across all Scrum boards automatically.

Professional Narration

Every verdict includes a precision-written QA summary. Not a raw data dump — a professional narrative explaining what was checked, what passed, and what to fix.

Regression & Audit Trail

Save verified stories to a regression suite. Export a Requirements Traceability Matrix as CSV. Every check is auditable and reproducible for compliance.

How It Works

Three steps from AC to
verified Salesforce

No setup wizards. No test scripts to maintain. Open a Jira issue, and TrueStory does the rest.

01

Write your requirements

Write acceptance criteria in Jira the way you always have. TrueStory understands plain English — field labels, API names, or a mix of both.

Jira Story · SCRUM-142
Acceptance Criteria:
• Discount_Percent__c exists on Opportunity
• Deal_Desk_Status__c picklist includes Pending, Approved, Rejected
• When Discount exceeds 30%, save must be blocked without approval
• Approval_Notes__c on Opportunity page layout
02

TrueStory builds a plan

Constraints are detected automatically. Field references are resolved against your org's live metadata. A verification plan is built with zero manual setup.

Verification Plan · 4 requirements
Discount_Percent__c field must exist on Opportunity
Discount_Percent__cexists
Deal_Desk_Status__c must include Pending, Approved, Rejected
Deal_Desk_Status__cpicklist
Discount > 30% must block save without approval
Discount_Approvalvalidation
Approval_Notes__c visible on Opportunity layout
Approval_Notes__clayout
03

Tests run against Salesforce

Metadata checks query the Tooling API. Behavioral tests create records and verify validation rules fire. Clear pass/fail per requirement.

TrueStory
ProPROJ-142
All 4 requirements verified
Story is ready for release
PASSDiscount_Percent__c field exists on OpportunityDiscount_Percent__c
PASSDeal_Desk_Status__c picklist includes Pending, Approved, RejectedDeal_Desk_Status__c
PASSWhen Discount exceeds 30%, save is blocked without approvalDiscount_Approval
PASSApproval_Notes__c visible on Opportunity page layoutApproval_Notes__c
All deal desk controls verified. Discount validation rule fires correctly. Approval picklist and page layout confirmed.
Story Readiness0%
✓ Ship it4/4 requirements · 8/8 checks
Post to JiraAdd to RegressionExport
Constraint Types

19 constraint types.
All from natural language.

Write acceptance criteria in plain English. TrueStory detects the constraint type and builds the right checks automatically.

Trusted by Salesforce teams

Built on enterprise-grade infrastructure with security-first design.

Atlassian Forge Native

Runs inside Atlassian's sandboxed runtime. No external servers, no data leaving the platform.

OAuth 2.0 Only

Never sees your Salesforce password. Tokens encrypted in Forge Storage. Revoke access anytime.

Built by Salesforce Engineers

Designed by architects who've spent years building and verifying Salesforce orgs for enterprise teams.

Zero Misleading Failures by Design

If TrueStory says FAIL, it's real. Infrastructure errors are never misreported as spec violations.

Why TrueStory

Manual QA vs.
automated verification

See what changes when every acceptance criterion is verified automatically.

AspectManual QATrueStory
CoverageWhatever you remember to checkEvery AC line verified systematically
Speed5-15 min per story, more for complex orgsUnder 10 seconds per story
ConsistencyVaries by person and dayDeterministic — same input, same result
Audit trailScreenshots, maybe a spreadsheetFull traceability matrix, exportable CSV
Drift detectionDiscovered in productionCaught before release
Behavioral testingManual clicks through the UIAutomated record creation + validation
ScaleSlows down as org growsHandles any org size, any sprint
Pricing

Start free.
Scale when you're ready.

Every plan includes the core verification engine. Upgrade for behavioral testing, dashboards, and AI-powered analysis.

Free
$0forever

Instant proof every requirement is built right. No credit card required.

Get Started Free
  • 10 stories per month
  • All 19 constraint typesfields, validation rules, layouts, formulas, and more
  • Behavioral testingcreates real records to test save logic
  • Deep metadata analysisFLS profiles, page layout placement
  • Readiness scoringper-story quality gate
  • Post results to Jira
  • Single org connection
  • AI-powered analysis
Team
$199/mo per site

Full automated QA for every story your team ships.

Start Free Trial
  • Everything in Free
  • Unlimited stories
  • Sprint & release dashboard
  • Regression suitetrack verification across releases
  • Professional QA reportsverdict summaries posted to Jira
  • CSV & compliance export
  • Multi-org connections
  • Email support
Most Popular
Pro
$399/mo per site

AI that reads your stories, builds test plans, and knows what to look for.

Get Early Access
  • Everything in Team
  • AI-powered analysishandles messy, unstructured AC
  • Intelligent test plan generation
  • Conversational follow-upask questions, adjust plans mid-session
  • Multi-provider AIClaude, GPT, or Gemini — bring your own key
  • AI-generated insightscontextual recommendations per finding
All plans billed per Jira Cloud site. Cancel anytime.
Need a custom plan for your org? Talk to us
FAQ

Common questions

Everything you need to know before connecting your org.

For metadata-only checks (field exists, picklist values, page layout), no records are touched. For behavioral tests (validation rules, required fields), TrueStory creates temporary test records, verifies the constraint fires, then deletes them. We strongly recommend connecting a sandbox org.
TrueStory connects to any Salesforce org via OAuth. However, we strongly recommend using a sandbox for behavioral testing. Metadata-only checks are read-only and safe for production. Behavioral tests create temporary records that may trigger automations.
TrueStory uses deterministic regex pattern matching — not AI or LLMs. Each of the 19 constraint types has a defined pattern. Same input always produces the same result. The Pro tier adds optional AI-powered analysis via your own API key (BYOK).
Any edition with API access enabled. TrueStory uses the Tooling API and REST describe endpoints, which are available on Enterprise, Unlimited, Developer, and most Professional editions with API access.
No. TrueStory runs entirely within Atlassian Forge. Your Jira and Salesforce data stays between Forge and your connected Salesforce org. The Pro tier (BYOK) sends story context to your chosen AI provider using your own API key — this is opt-in and fully under your control.
TrueStory is built on Atlassian Forge and requires Jira Cloud. Jira Server and Data Center are not currently supported.
Typically under 10 seconds per story. Metadata checks run via Tooling API queries, and behavioral tests create and verify test records in parallel where possible.
TrueStory's metadata index maps field labels to API names. If multiple fields match a label, the requirement is marked UNMAPPED and TrueStory suggests candidates. You can disambiguate by using the API name (e.g., Opportunity.Amount__c).

Ready to automate your
Salesforce QA?

Get early access to TrueStory. Start free, upgrade when your team is ready. No credit card required.

Free plan available · Installs in Jira Cloud in 2 minutes