Skip to main content

Create & Manage Projects

Projects are the container for everything your team does inside TestFish—test repository, requirements, test runs, defects, automation, and analytics. They combine access control, configuration, and execution tooling in one place.

Creating a project​

When you create a project you provide:

  • Name & description – Displayed across the workspace, dashboards, and exports.
  • Cover photo (optional) – Used on project cards and the home dashboard.
  • Status flags – is_completed to archive work without deleting it and is_public to expose the project to everyone in the organisation.
  • Default role – Required when is_public is enabled. Determines what members can do when they land in the project.

After creation you can immediately:

  • Assign members or groups with tailored roles per person/group.
  • Star the project for quick access from the global home page.
  • Attach project templates for reusable suites, plans, and configurations.
  • Seed workflow states – Projects automatically pull in the organisation’s default workflow states for test cases, test runs, defects, and requirements. You can enable/disable or reorder them per project.
  • Configure review policies – Decide if test case creation, updates, or deletion require approval, the number of reviewers, and whether anyone can merge changes.
  • Enable integrations – Link the project to organisation-level Jira, GitHub, or ClickUp integrations by creating project integration categories with the right mapping (project, list, repository, issue type, etc.).
  • Provision automation tokens – Generate scoped API tokens (CI/CD, automation, webhooks, integration, Jira Forge) from the project settings.

Visibility & access control​

  • Public projects inherit access from the selected role. Everyone in the organisation can see the project, but only the permissions granted by that role apply.
  • Private projects are invitation-only. Assign users or groups with role-based permissions for granular control.
  • Organisation access levels (Owner, Admin, Regular) still apply—Owners/Admins can always access configuration surfaces regardless of project visibility.

Project navigation highlights​

  1. Overview – Execution analytics, defect and requirement widgets, milestone status, and assigned work.
  2. Repository – Nested suites, rich test cases with revision history, review workflows, AI generation, and traceability.
  3. Test Runs – Manual and automated runs, reruns, time tracking, and detailed execution drawers.
  4. Defects – Kanban board with drag-and-drop workflow states, filters, attachments, and integration sync.
  5. Requirements – Hierarchical work items, board views per workflow state, and coverage indicators.
  6. Milestones & analytics – Track releases, environments, and automated metrics; export CSV/PDF reports.
  7. Settings – Configure workflow states, review rules, custom fields, integrations, automation tokens, and templates.

Use projects to separate products, teams, or customers. They keep permissions tight while giving testers and stakeholders a single source of truth for quality status.