Evidence you can follow
Exact-source links, many-to-many task/QA relationships and explicit verification states.
Follow the evidenceThe product
Write the context, turn it into accountable work, plan the delivery, and retain the evidence of what was tested.
Write living requirements and decisions with hierarchy, contextual comments, revisions, comparison and restoration. Link work to an exact block or selected text.

Configurable boards, assignees, dependencies, subtasks, checklists, labels and bulk actions keep delivery organized.

Organize suites and structured cases, execute runs, retain revisions and turn failed or blocked evidence into linked defects.

Coordinate cycles, milestones and releases. Use timelines, calendars, time tracking and effort reports to inspect delivery.

Exact-source links, many-to-many task/QA relationships and explicit verification states.
Follow the evidencePortfolio, health updates, workload, capacity and formal approvals provide a shared view of delivery.
Configure task rules and recurring work. QA signals do not silently complete tasks.
When enabled, draft writing and proposed tasks or Test Cases for explicit review and acceptance. Availability depends on deployment configuration.
Read-only GitHub evidence supports one repository per project. Scoped API access includes projects:read, tasks:read and test-results:write; JUnit ingestion matches existing cases and diagnoses unmatched results.
Import compatible CSV/XML and export your library. Yetea consumes CI results; it does not execute your CI tests.
Explore test managementFeature availability depends on the current offer and, for integrations and AI, deployment configuration. See current access and proposed plans.
Ship confidently. Breathe easy.
Keep the requirement, the work, and the test evidence together. Start with one real project.