TestKase
TestKase
|Docs
IntegrationsBuilt-in

Built-in

Manage requirements and defects natively in TestKase without external integrations.

Overview

TestKase includes full built-in requirement and defect management for teams that do not use an external issue tracker like Jira, GitHub, or GitLab -- or for teams that prefer to manage everything in one place. With the built-in option, you can create requirements, track defects, organize them into folders, and link them to test cases and test cycles without configuring any external integration. Everything lives inside TestKase, giving you a self-contained test management workflow from requirements through execution to defect resolution.

No setup required

Start managing requirements and defects immediately with zero configuration

Full requirement management

Create, prioritize, and track requirements with statuses, priorities, and attachments

Defect tracking

Log defects during execution or manually, and track them through resolution

Folder organization

Organize requirements and defects into folder hierarchies for easy navigation

When to Use Built-in

The built-in option is the right choice when:

  • Your team does not use an external issue tracker -- You do not have Jira, GitHub Issues, or GitLab Issues in your workflow, or your team manages work outside of those platforms.
  • You want a self-contained test management workflow -- Requirements, test cases, test cycles, defects, and traceability all live in TestKase with no external dependencies.
  • You need requirements and defects managed alongside test cases in one tool -- Having everything in a single platform simplifies onboarding, reduces context switching, and keeps traceability tight.

When to Use an External Integration Instead

If any of the following apply, consider connecting TestKase to an external platform:

  • Your backlog lives in Jira, GitHub, or GitLab -- If your team already tracks requirements or user stories in an external tool, syncing them into TestKase avoids duplicate data entry and keeps both systems aligned.
  • You need bidirectional sync with your issue tracker -- External integrations automatically sync status, priority, and comments between TestKase and the connected platform.
  • Your developers work primarily in an external platform -- Pushing defects to Jira, GitHub, or GitLab puts bug reports where developers already work, reducing friction.

You can switch between built-in and external integration at any time. If you start with built-in management and later adopt Jira or GitHub, your existing requirements and defects are preserved -- you simply connect the integration in project settings.

Next Steps