Skip to main content

Jira

TestFish connects to Jira so defects raised in projects can sync automatically to your Jira site (Cloud or Data Center via Forge app/API token).

Organisation-level setup​

  1. Go to Configuration → Integrations → Jira.
  2. Authorise the TestFish Jira app or provide the required credentials (client ID/secret or API token depending on your plan).
  3. Test the connection; TestFish stores tokens securely and monitors expiry.

Project-level mapping​

Once Jira is connected organisation-wide, open a project and configure Project → Integrations → Jira:

  • Project – Choose the Jira project key to sync with.
  • Integration type – Decide whether the mapping is used for defect sync, requirement links, or automation triggers.
  • Issue type – Default issue type for new defects created in TestFish.
  • Statuses – Map TestFish workflow states to Jira statuses and optionally a resolution for "Done" transitions.
  • Priorities & severities – Align severity/priority fields so they stay in sync across systems.
  • Assignees – Pull the Jira user list to mirror assignments when you update a defect.

Sync behaviour​

  • Creating or updating a defect in TestFish pushes the change to Jira (title, description, attachments, assignee, status, priority, severity).
  • The Jira issue key is stored on the defect card and shown in the list view; clicking opens Jira in a new tab.
  • Manual sync (Sync Defects button) re-fetches status, assignee, and resolution if the issue was updated in Jira.
  • Deleting a defect in TestFish does not delete the Jira issue; it simply stops syncing.

Tips​

  • Use scoped API tokens (Forge app token or OAuth credentials) with the jira_app token type for least-privilege access.
  • Keep workflow mappings up to date if you add new columns to the TestFish board.
  • Pair Jira sync with webhooks so updates made directly in Jira reflect instantly in TestFish.