Skip to main content

Defects

TestFish ships with a full defect management module that can operate standalone or alongside external trackers like Jira, GitHub, and ClickUp. Every project gets its own board powered by custom workflow states and drag-and-drop ordering.

Creating a defect​

Capture the following details:

  • Title & rich description (TipTap editor with screenshots, code blocks, links).
  • Severity & priority – Customisable enums for triage.
  • Workflow state – Columns on the kanban board; reorder or rename states per project.
  • Milestone – Tie issues to release checkpoints.
  • Assignee & reporter – Track ownership; reassignment triggers in-app notifications.
  • Due date – Enforce SLA-driven work.
  • Test links – Associate the defect with the originating test run and test case for traceability.
  • Attachments – Upload evidence directly from the run or repository.
  • Tags – Classify defects across projects for analytics.

Working the board​

  • Kanban view – Drag cards between workflow states or reorder within a column. Positions persist for prioritisation.
  • Filtering – Slice by assignee, milestone, severity, priority, status, tags, test run, or linked test case.
  • Detail drawer – Open a card to see history, attachments, linked executions, requirement relationships, comments, and integration metadata.
  • Notifications – Assignments trigger Noticed notifications and optional external webhooks.

Integrations & sync​

  • Two-way sync – When a project is mapped to Jira, GitHub, or ClickUp, creating or updating a defect pushes changes upstream (title, description, assignee, workflow state) and stores the external link on the card.
  • Manual sync – Use the Sync Defects button to reconcile data if something changes outside TestFish.
  • External links – Link to existing third-party issues without duplicating them; they still appear in traceability views.

Tips​

  • Configure workflow states per project (Configuration → Workflow States) to mirror your team’s process.
  • Use severity to capture impact and priority to capture urgency so analytics remain meaningful.
  • Attach logs or console output directly from automated runs—attachments travel with the defect even if synced externally.