Skip to main content

Managing Integrations

TestFish integrates with several platforms so you can keep QA activities in sync with the rest of your product stack.

Available integrations​

  • Jira – Two-way defect sync, requirement backlinks, and Jira Forge automation.
  • GitHub – Create/link GitHub issues, trigger workflows, and keep assignments aligned.
  • ClickUp – Sync defects into ClickUp tasks with status/priority mapping.

How integrations are structured​

  1. Organisation-level – Owners/Admins authorise the platform (OAuth, app installation, or API token). Tokens are encrypted and monitored for expiry. You can revoke integrations anytime.
  2. Project-level – Projects create integration categories that define scopes (defects, requirements, automation). Each category stores mapping details (project/list/repo, statuses, assignees, etc.).
  3. Automation – Use webhooks or API tokens to trigger CI/CD jobs, post execution results, or sync custom data.

Best practices​

  • Use dedicated integration API tokens (token type integration or webhook) so you can rotate credentials without affecting users.
  • Keep workflow mappings up to date in both systems—when you add a new TestFish workflow state, map it to an external status.
  • Test integrations in a staging workspace before rolling out to production teams.
  • Review the audit log after enabling an integration to confirm the sync behaviour aligns with your expectations.