Partner-supported, by the people who build it.

• The released app: installation and permissions, test management (library, plans, cycles, runs, defects, coverage, export), the Migration Center and licensing questions. Sites with up to 10 Jira users are on the free tier and get the same support.
• The Warden: why a change is HELD or INCOMPLETE, what the next action is, and how to submit JUnit XML, SARIF or JSON evidence from your CI so it counts against the exact build.
• Developer pilot lane: the Developer API, PowerShell client, MCP server and GitHub action are pilot capabilities outside the Marketplace V1 release. Pilot participants get help on a best-effort basis through the same channels.
• Not covered: Atlassian platform incidents (see Atlassian's status page), the internals of your own CI, test runners or scanners, and decisions your organization makes from a verdict. A third-party tool's pass is evidence for The Warden to weigh, so we can explain how it was weighed but not change it.

• Documentation first: the TestWarden documentation covers installation, every workspace, The Warden's decision model, CI evidence submission and troubleshooting.
• Email: [email protected] for product questions, defects, installation and licensing help, or use the contact form.
• Telephone: 949-750-6931 during support hours. Email or the contact form gives us the detail we need to act, so please follow up a call with one of those.
• In-app: the ? (Help and feedback) button in TestWarden shows the app version and lets you copy a diagnostic reference to include in your email.

1. Your Jira Cloud site URL (for example your-site.atlassian.net).
2. The TestWarden app version and diagnostic reference from Help and feedback.
3. The workspace and action involved (for example “Plans & Runs → Run again”).
4. What you expected and what happened, with the exact message shown.
5. Steps to reproduce, and whether it affects one user or everyone on the site.
6. For migration issues: the source type, the preview counts and the row numbers reported as skipped or failed. Please do not email customer exports containing personal data; we will arrange a secure path if a file is needed.

Support hours: Monday–Friday, business hours. Business hours are stated in the Pacific time zone (US) unless otherwise agreed.

Target initial response: within 1 business day, Monday–Friday.

TestWarden does not currently offer 24/7 staffed support or a contractual uptime SLA. Response targets describe our operating intent and are not a contractual service-level agreement.

Report a suspected data-integrity or availability problem with "Critical" in the subject line. Critical reports are triaged first during business hours and worked continuously until the product is usable again.

Because TestWarden runs on Atlassian Forge, platform availability incidents are reported on Atlassian's status page; TestWarden-specific defects are fixed and released to customers, and we confirm the fix version with you.

Please report suspected vulnerabilities or data-exposure concerns separately to [email protected] rather than to general support. See the Security page for what to include and how reports are handled.

Keeping AIO Tests, Xray, Zephyr Scale, TestRail or Azure DevOps? You do not need to migrate. Today we can help you submit a complete JUnit XML, SARIF or JSON report from your CI so The Warden evaluates it against the exact build. Read-only provider connectors are in source and under acceptance; developer-preview integration testing is available by arrangement, subject to readiness. Tell us your tool, edition and CI system through the contact form, and see Integrations for the current status of each provider.

Moving test cases from Xray, Zephyr Scale, AIO Tests (via CSV export) or spreadsheets? Start with the migration documentation and the preview step in the Migration Center, which reports what will import and what will be skipped before anything is written. If a preview surprises you, email support with the source type and the skipped-row reasons and we will help you adjust the export or mapping. Migration help is included; there is no separate migration edition. Planning a larger move first? Use the migration contact form.

• No changes received yet / connecting CI
• Evidence rejected by the App REST API
• A change stays HELD after a fix
• Cannot archive, restore or migrate (roles)
• Jira issue created but not linked
• The app is read-only (subscription inactive)

TestWarden is publicly available on Atlassian Marketplace. Get TestWarden on Marketplace to start installation or an evaluation. For guided onboarding, pricing and Founding Customer questions, use the contact form; Pricing has the published figures. Tell us your Jira site size, your current test-management tool and your CI system.