Product Updates

What's New

New features and improvements shipped to TestCollab.

Feature

Default Assignee for Test Cases

Name the tester who normally runs a test case, and every plan that includes it starts out already assigned.

A test case can now carry a default assignee - the project member who normally executes it. Whenever that case is added to a test plan the assignment comes with it, so the plan is already assigned before anyone opens the assignment step.

- Set it wherever you work with test cases - on add and edit, in bulk edit, and as a column and a filter on the test cases grid. It is included in the CSV and PDF exports.
- The plan keeps its own copy - the default is copied in when the case is added, so changing it later never rewrites plans that already exist. A default pointing at someone who can no longer execute is skipped, and the case lands unassigned.
- Automatic assignment fills the gaps - the assignment step now only distributes cases that are still unassigned. Tick Apply assignment rules to all test cases to replace everything instead, and it tells you how many assignments that will overwrite.
- Removing a member asks what happens to their work - a project member who still holds assignments cannot be removed silently. The dialog lists what they hold and requires a choice: mark the work unassigned, or hand it to another member. The transfer runs in the background, and completed executions, results and history are never rewritten.

Pipelines get the same control. In tc-cli v1.19, tc createTestPlan keeps each case's default assignee and gives --assignee-id only the cases without one. Pass --override-assignees to assign every case in the plan instead.
TCV-6779TCV-6888TCV-6889TCV-6890TCV-6891TCV-6892TCV-6893TCV-6894TCV-6895TCV-6897TCV-6898TCV-6900TCV-6913
API 85bd9395 !226
UI 8d4969ae !221
CLI c235a7b6 !21
Fix

Entra ID Access Revoked Right Away

Removing someone from your Entra enterprise app now cuts off their TestCollab access immediately.

Two fixes to Microsoft Entra ID single sign-on (Enterprise):

- Removal takes effect immediately - TestCollab checks the live Entra application assignment when it issues a session, and re-checks it for sessions already in use. Someone removed from the enterprise app loses access straight away instead of keeping their last role until their token expires. A check that cannot complete denies access rather than allowing it.
- Provision on demand applies role changes at once - when a user's mapped groups and app roles are all gone, that run drops them to the configured default role instead of leaving the old role in place until their next login. Project roles you assigned by hand are left alone, and only an explicit removal in Entra deprovisions the account.
TCV-6907TCV-6910
API 85bd9395 !226
UI 8d4969ae !221
Improvement

Step Count in Test Case CSV Export

The test cases CSV export now carries the No. of Steps column shown on the grid.

Exporting test cases to CSV now includes No. of Steps for each case, using the same count as the grid column. Sizing execution effort outside TestCollab no longer means opening each case to count its steps.
TCV-6705
API 85bd9395 !226
Feature

tc-cli v1.18: Report Each Case As It Finishes

AI agents can report each test result the moment a case finishes, instead of at the end of the run.

The new tc reportCase command reports one assigned execution as soon as it finishes, with its status, comment, time taken and attachments. Each result appears in TestCollab immediately, so a run that stops halfway keeps everything reported up to that point. tc getTestPlan --test-plan-run-id now returns the exact executions assigned to the caller plus the project's active statuses, including custom ones, so an agent knows what to report and which status names it can use. tc report still handles bulk upload of a finished JUnit or Mochawesome file.
CLI 982879f5 !20
Improvement

MCP Server Setup for Codex

Connect the TestCollab MCP server to Codex and manage your tests from the terminal.

The setup guide now covers Codex alongside Claude Code, Claude Desktop and Cursor. Register the server with a single codex mcp add testcollab command, or add it to ~/.codex/config.toml so it loads in every project. Once connected, Codex can read and create test cases, suites and test plans in your TestCollab projects. See the MCP server integration page for the full tool list.
MCP b61f4bc0 !8
Feature

Automatic Requirement Sync for GitLab, Azure DevOps and Asana

GitLab, Azure DevOps and Asana requirements now stay current automatically, with faster linking and consistent traceability across test cases and builds.

GitLab, Azure DevOps and Asana now join Jira in automatic requirement syncing, with last-sync status and a Sync Now control in Requirement Settings. The requirement picker searches synced items by key or title and can refresh directly from the connected source without saving unused results. Renames and deletions stay consistent across test case grids, the Traceability Matrix and build detail, while build traceability now works with Jira, Azure DevOps, GitLab, Asana and TestCollab requirements. Elite trial workspaces can also select Asana as their requirements manager.
TCV-6780TCV-6840TCV-6862TCV-6865TCV-6874TCV-6875TCV-6877TCV-6878TCV-6879TCV-6884
API 40393727 !223
UI ab277a03 !219
API 7520be90 !231
Feature

Link Test Cases to Azure DevOps Work Items

Link and unlink a requirement directly from a test case, for Azure DevOps, Jira, GitLab and every other connected requirement source.

You can now attach a requirement to a test case from the test case side pane, and unlink it from either side, without leaving the page. It works the same way for every connected requirement source, so an Azure DevOps work item links exactly like a Jira issue does. Requirements that are not linked to any test case are called out on the requirements index, so a coverage gap is visible before you open the Requirements Traceability Matrix.
TCV-6718
API e50239ba !229
UI cbe69d09 !227
Feature

Turn Off AI Features for the Whole Company

A single company-level setting hides every AI surface in TestCollab, for teams whose policy does not allow AI-assisted tooling.

Some teams cannot use AI features for policy or compliance reasons. A company administrator can now opt out once in company settings, and every AI surface disappears across the app rather than staying visible and disabled. This is the setting to point at when a security review asks whether AI can be switched off.
TCV-6854
API e50239ba !229
UI cbe69d09 !227
Feature

tc-cli v1.17: Upload Test Artefacts with `tc report`

Screenshots, traces and logs from a CI run now land on the test case execution, in the same place a manual tester's evidence goes.

A failed automated case used to give a tester a pass or fail and nothing else. tc report now reads [[ATTACHMENT|path]] marker lines from each JUnit test case and uploads those files onto that case's execution.
tc report --project 45 --test-plan-id 123 --result-file results.xml
The marker is the Jenkins JUnit Attachments convention, which Azure DevOps also reads, so Playwright, Cypress and most CI reporters work without changes. Attachments never block a release: a missing or oversized file is skipped with a warning, and the results are still reported.
TCV-6853
CLI 8c51704c !19
Feature

Builds and Releases (Elite and above)

Record the build a test plan ran against, then see which version was verified, by what, and what is left before you ship.

A Build is now a first-class record in TestCollab, managed under Test plans alongside Releases. Create a build for the version you deployed, link test plans to it, and every result those plans produce is tied to that version.

- Build detail traceability - one page per build showing its linked test plans, what ran against it, what passed, and when each plan was executed.
- Build-aware traceability and readiness - filter the Requirements Traceability Matrix by build, and see on Release Readiness which build each plan was verified on.
- Builds attach to releases automatically - set a version pattern on a release and matching builds are linked to it, so a release shows every build it contains.

Builds can be recorded straight from a pipeline with tc createBuild, or created by hand.
TCV-6720TCV-6722TCV-6723TCV-6726TCV-6727TCV-6787TCV-6801
API 7921fff4 !212
UI 836dc6a6 !206
Feature

See How Each Test Result Was Produced

Every result now records whether a person ran it or a pipeline did, so plan summaries and build reports show how much of your testing is really automated.

Results now carry a Run Mode: manual, CI or API. The run grid shows it as a column, and plan summaries and build detail break their results down by it, so automation coverage comes from real evidence rather than an estimate. Run By is filterable in the run grid and appears on the execution log, which answers "who or what verified this build" without opening each case one by one. Results uploaded by tc report are stamped automatically from the pipeline that sent them.
TCV-6814TCV-6815
API 7921fff4 !212
UI 836dc6a6 !206
CLI 4391c1dc !17
CLI 76a4feee !18
Improvement

Risk Register and Matrix Improvements

The risk matrix is colour-coded by exposure band and clicks through to a filtered register, and each risk shows whether its linked tests pass, fail or never ran.

Follow-up work on Risk-Based Testing:

- Verification status per risk - each risk shows whether the test cases linked to it passed, failed or were never run, so a failing or untested risk stands out in the register.
- Click a matrix cell to see its risks - cells are coloured by your configured exposure bands and open the register filtered to that cell. Uncovered risks are surfaced in both views, and you can create a test plan for them straight from the register.
- Every risk has its own URL - link a specific risk from a ticket, a document or a chat message and it opens directly.

The project's configured exposure bands now drive the register, matrix, summary, Risk Level filter and the test case Risk Level pill consistently.
TCV-6684TCV-6685TCV-6686TCV-6687TCV-6836TCV-6839TCV-6861
API 7921fff4 !212
UI 836dc6a6 !206
API e50239ba !229
UI cbe69d09 !227
Fix

Fixes Across Reports, Run History and Traceability

Fixes to test plan reports, the Run History tab, the Traceability Matrix, and the Builds and Releases lists.

- Test plan reports show pass and fail status for each dataset iteration.
- The Run History tab no longer lists runs that were never executed.
- The Traceability Matrix shows only the work item types selected in your requirements configuration.
- Builds and Releases lists are paginated with a rows per page selector.
- Jira issue search works when the defect connection is set to a single issue type.
- User avatars align correctly in grid columns and dropdowns.
TCV-6666TCV-6822TCV-6824TCV-6825TCV-6831TCV-6841
API 7921fff4 !212
UI 836dc6a6 !206
Feature

tc-cli v1.14: Record Builds from Any CI Pipeline

The new `tc createBuild` command tells TestCollab which version your pipeline just built, and `tc createTestPlan` can tie a plan to that build.

One command works the same in Azure DevOps, GitLab CI, Jenkins and GitHub Actions, with no extra permissions needed in your DevOps environment.
tc createBuild --project 45 --version $BUILD_VERSION --environment staging
The build is matched on version and created only when missing, so a re-run never records the same version twice. tc createTestPlan --build then ties a plan to that version, and its release is filled in from the build. The provider, the pipeline run URL and the commit are detected from the CI environment, so the step stays a one-liner. This replaces the Azure DevOps deployment sync, which has been retired.
TCV-6788TCV-6794
CLI 2d63dfd5 !15
CLI cc8ddfd2 !16
Improvement

Azure Test Plans Import Improvements

Large Azure DevOps migrations now show accurate counts and visible progress, and no longer send an email for every imported test plan.

Follow-up work on the Azure Test Plans migration. Validation now reports the real number of plans, suites and test cases that will be imported, the import shows progress while it runs, and each imported plan gets a parent suite named after the plan. Importing a large repository no longer creates an assignment task, a notification and an email for every plan, so a migration of a few hundred plans does not flood your team's inboxes.
TCV-6667TCV-6782TCV-6786
API 328136e6 !224
API be770756 !225
UI e1daa4ea !220
Feature

Import Test Plans and Test Cases from Azure DevOps

Move an Azure Test Plans repository into TestCollab with a guided migration that brings across plans, suites, test cases, steps, tags, and useful work item metadata.

Azure Test Plans structure moving into an organized TestCollab test repository
A new full migration under Settings > Import & Migration connects directly to an Azure DevOps project and brings its test plans, suite hierarchy, test cases, steps, tags, and supported metadata into TestCollab. Shared Steps are expanded into each case, a default assignee can be selected for imported plans, and an optional setting also brings across Test Case work items that are not part of any Azure test plan. The migration runs in the background with progress and a final summary, so you can leave the page while a larger repository is imported. See how the Azure Test Plans migration works →
TCV-6667
Feature

AI QA Agent Directory

Explore 10 specialist agents for regression, smoke, end-to-end, API, security, performance, accessibility, code, compliance, and SEO checks.

The new AI QA Agent Directory helps teams choose a focused agent for the quality signal they need. Each agent page explains what it checks, the evidence it returns, and how it fits into a release workflow, including optional self-hosted deployment with an approved open-source model and webhook or scheduled execution. Read the launch announcement, or book a demo to map the right agents to your release process.
Feature

tc-cli v1.11.0: New `tc gate` Command for CI/CD Quality Gates

Fail a CI/CD pipeline on your TestCollab results. The new `tc gate` command turns a test plan into a quality gate for Azure DevOps, Jenkins, GitLab CI, or Ansible.

Automated results already flow into TestCollab through tc report. Now tc gate lets a pipeline block a build or deployment when those results miss your bar.
tc gate --project 45 --test-plan-id 123 --fail-on failed
The command reads the test plan's latest run and exits non-zero when the gate is not met, which fails the surrounding step. Because it is a plain command with an exit code, the same gate works in Azure DevOps, Jenkins, GitLab CI, GitHub Actions, and Ansible Tower.

- Choose what fails the build - any failed case (the default), failed or blocked, a cap on failures, or a minimum pass rate.
- Hold a deployment until QA signs off - --wait polls until the run finishes, then passes or fails the release.

Full setup, including a ready-to-use Azure DevOps pipeline, is in the quality gate guide.
TCV-6668
CLI d38e8c6d !11
Feature

Entra ID SSO and SCIM Provisioning (Enterprise)

Microsoft Entra ID joins Okta as a single sign-on provider, with group-to-role mapping and automatic user provisioning over SCIM 2.0.

Microsoft Entra ID (formerly Azure AD) joins Okta as a single sign-on provider, and can be required for everyone in the company. A company runs one provider at a time.

- Group and app role mapping - Map your tenant's security groups and app roles to TestCollab roles, across all projects or a selected set. Roles are recalculated from the user's groups at every sign-in, and roles you assigned by hand are left alone.
- SCIM 2.0 provisioning - Assigning someone to the TestCollab app in Entra creates or links their account. Unassigning them removes their access to that company only, so an account shared with another TestCollab company keeps working there.

Learn more about SSO and SCIM provisioning →
TCV-6661
API 2a1c92f7 !214
UI 57ad6f19 !207
Fix

Custom Fields Now Apply to Existing Issues and Requirements

Adding a custom field to the inbuilt issue tracker or requirements now backfills it onto records that already exist, not just ones created afterward.

A background job applies a newly created custom field to existing records. For inbuilt issues and requirements it referenced the wrong source column and errored, so the field was added to the project but never appeared on items created before it. The reference is corrected, so a new custom field now shows (empty) on all existing issues and requirements as intended.
API 4a606749
Feature

Risk-Based Testing (Enterprise)

Plan and prioritize testing by risk. A new Risks module adds a risk register, a likelihood x impact matrix, configurable scoring, and full traceability from risks to requirements, test cases, and defects - plus a Risk Level column that orders test execution by exposure.

TestCollab risk register: risks scored by likelihood and impact with colour-coded exposure bands
- Risk register and matrix - Track risks (prefix RK-) scored by likelihood x impact, grouped into colour-coded exposure bands, with a likelihood x impact heat map that filters the register on click.
- Configurable scoring - Project admins set risk statuses, types, likelihood and impact scales, and exposure-band thresholds.
- End-to-end traceability - Link risks to requirements, test cases, and defects, with two-way visibility from each linked item.
- Risk-weighted execution - A Risk Level column on test plans sorts and filters cases by their highest linked-risk exposure, so the riskiest run first.
- Readable IDs - New per-company TC-, TP-, and RK- identifiers replace raw row numbers.

Read the risk-based testing guide →
TCV-6606TCV-6619TCV-6620TCV-6621TCV-6629TCV-6649TCV-6655
UI ab00e3c3
API 75c2256d
Feature

Import Test Cases from Xray for Jira

A guided wizard imports your Xray for Jira test repository into TestCollab. Connect with your Jira and Xray Cloud credentials, pick a project, preview what will be created, and bring across folders, test cases with steps, test sets, and test plans.

TestCollab now has a native importer for Xray for Jira, so you can migrate without CSV exports or manual reformatting. Authenticate once with your Jira and Xray Cloud API credentials, choose the project to migrate, and the wizard maps your Xray test repository folders to TestCollab suites and brings across test cases (including their steps), test sets, and test plans. You see a preview of what will be created before the import runs, and the importer tracks an ID mapping so you can re-run it safely without creating duplicates.
TCV-6493
UI 12144b7d
API 2f94f743
API 29b68cfb
Feature

Export the Requirements Traceability Matrix to CSV

Export your full requirements-to-test-case coverage matrix to CSV straight from the Traceability Matrix view. The export respects the filters you have applied and can optionally include uncovered requirements so coverage gaps show up in the data.

A new Export CSV button on the Requirements Traceability Matrix downloads the whole matrix: each requirement alongside its linked test cases and coverage status. The export honours the filters currently applied to the matrix, and a single toggle lets you include requirements that have no linked test cases (marked 'Uncovered') so gaps are visible in the spreadsheet. Large matrices are generated in the background and the download is ready when the export finishes, so big projects export without timing out.
TCV-6597
UI 3b524ccd
API b06ac0b6
Feature

Custom Reports: Configurable Widget Layout, Issue Dataset, and Date Trends

The Custom Reports builder gains a configurable dashboard layout (per-widget placement, size, and chart type), an Issue dataset for the inbuilt defect manager, automatic stacked bar/column charts when two dimensions are picked, and date-grouped trends like 'test cases executed per day'.

A bundled release of Custom Reports improvements, driven by enterprise feedback on what reports were missing and how the dashboard view of them should behave.

- Configurable widget layout on the project dashboard - Pinned report widgets are no longer fixed in a single grid slot. Each widget now has its own placement (row/column), size (width/height), and chart type, persisted via a new dashboard widget layout API. Customers can put 'Test Execution by Department' and 'Test Execution by Module' on separate full-width rows, resize a widget to span the dashboard, or switch its chart type without rebuilding the underlying report.
- Issue dataset - Inbuilt issues are now a fourth dataset alongside Test Cases, Test Plans, and Executions, gated to projects using the inbuilt defect manager. Pivot on standard fields (status, priority, created by, issue key, dates) or any defect custom field. Status and priority values come from the project's own defect_field_options, so charts reflect each project's configured workflow.
- Linked test case / suite / test plan dimensions - Within the Issue dataset, group by the test case, test suite, or test plan an issue is linked to - useful for tying defect counts back to coverage. Joins are added only when these dimensions are selected, so reports that don't need them avoid row fan-out.
- Stacked charts and per-widget chart type - Column and bar charts auto-stack when a report has two dimensions (e.g., issues per department × status). Each widget now has its own chart type selector - column, bar, line, or pie - and the choice is persisted in the report definition, so a single report can mix chart styles across widgets.
- Date dimensions and date trends - Date fields (run_on on executions, created_at on every dataset) can now sit on the X-axis, grouped by day. Line charts are auto-selected when the primary dimension is a date, and date categories sort chronologically - so 'test cases executed per day' and similar trend reports work out of the box.
TCV-6536TCV-6537
UI 59508fa2 !190
API 951fd48f !196
UI 1a90fd71
API ff1fc92c
API 1b7e0d65
API 453b3cac
API 2aea08a2
Feature

Requirements CSV Export

Export project requirements to CSV from the Requirements page. Choose between visible columns or all columns, and toggle whether to include HTML tags in descriptions.

Project requirements can now be exported to CSV. A new export button on the Requirements page opens an Export CSV dialog where you can pick between exporting only the columns currently visible in the grid or all columns, and whether to keep HTML tags in description text.
TCV-6581
Feature

Comments on Inbuilt Issues

Issues now support a full comment thread with rich text, @mentions, email notifications, and a 5-minute author edit/delete window.

Inbuilt issues now have their own conversation thread, matching the comment system already on test cases, test plans, and executions.

- Comments section - A new section appears below the issue details on both the issue view and the Edit Defect page, with each comment showing the author's avatar, name, timestamp, and a count badge in the header.
- Rich text and @mentions - Comments support formatted text and @mentions of project members. Mentioned users, the issue assignee, and the issue creator all receive an email notification when a comment is posted.
- Edit / delete window - Authors can edit or delete their own comments within 5 minutes; after that, the controls disappear. Edited comments show an (edited) label. Company admins can edit or delete any comment at any time for moderation.
- Included in exports - Issue exports now include the comment thread, formatted as timestamp - User Name: comment text.
TCV-6567
UI 063bd61d !187
API 028e1545 !194
Feature

tc-cli v1.10.0: New `getTestPlan` Command for Agent-Driven QA

Fetch a curated test plan as agent-friendly JSON, designed to be consumed by AI coding agents (Claude Code, Cursor, Codex) that execute the cases via browser automation.

Hand-written E2E suites are expensive to maintain and manual QA is slow, but coding agents can now drive a real browser reliably. What they were missing is a structured plan of what to test. The new tc getTestPlan command provides exactly that.
tc getTestPlan --project 16 --test-plan-id 555 --output /tmp/plan.json
The command returns the plan and its test cases as clean JSON - HTML stripped from steps and descriptions, statuses mapped, per-configuration results included where the plan has a Browser × OS matrix. Progress messages go to stderr so stdout stays clean for piping to jq or directly into an agent.

Humans curate plans in TestCollab; the agent reads them via getTestPlan, executes via Playwright MCP / computer use, and uploads results back via tc report. The full pattern is documented in the new Agentic QA Guide.
CLI b6881c79
Improvement

User Avatar Display Format Setting

A new global setting controls how user avatars are labeled across the app - Initials, Full name, F. Lastname, or Firstname L. - so you no longer have to hover to see who's assigned.

Hovering over a circle of initials to learn who's assigned has always been a small but constant friction. Settings > General now has a User Avatar Display Format dropdown that controls labeling globally.

- Four options - Initials only (the previous default), Full name, F. Lastname, and Firstname L.
- Applied across the app - Issues, Test Cases, Test Plans, and Requirements grids; user-type custom field columns; the Test Case Review Information and Changelog tabs; the Test Plan index 'Assigned To' column and Summary tab; the project Activities timeline; and assignment events in the activity log all respect the chosen format.
- Compact lists unchanged - Multi-user avatar stacks (e.g., the Projects page Team column) continue to show initials so layout doesn't break. Surfaces that already showed full names are unchanged.
TCV-6564
UI 69598a64 !186
UI e7381489 !185
API 474ec12c !193
Feature

Never-Assigned Test Cases: Coverage-Gap Tracking

A new 'Never Assigned' flag identifies test cases that have never had anyone assigned to run them. Surfaced as a dashboard metric, a grid column, and a filter.

Test cases that have never been assigned to anyone - through any test plan, configuration, or execution - are a strong signal of coverage gaps. Project owners can now find them at a glance.

- 'Never Assigned' flag - Computed for every test case from the full assignment history. The flag is set when the case is created and flips to 'No' the first time anyone is assigned. It also recomputes when assignments are removed (clearing an assignee, deleting a test plan or test case row), so it accurately reflects current state.
- Dashboard metric - The project dashboard surfaces a new Never Assigned Test Cases count.
- Grid column and filter - The Test Cases manage page (/project/:id/manage) gets a hidden-by-default 'Never Assigned' column with Yes/No values, plus a multi-select Yes/No option in the filter pane.
TCV-6566
UI 1642dfa3 !184
API 29536eef !192
Fix

Consistent Status Colours Across Custom Reports

Execution status colours and legend ordering are now identical across the report builder and pinned dashboard widgets.

Previously the same execution status (Passed, Failed, Blocked, etc.) could render in a different colour or legend order depending on whether you were viewing the custom report builder, a preview, or a pinned widget on the project dashboard. The fix moves status colour, status order, and dimension behaviour into a single shared utility so every chart pulls from the same source. No setting changes required - every existing report becomes visually consistent on its own.
TCV-6535
UI acaa3154 !183
Feature

Issue Reporter Label and Activity Timeline

Issues now show who reported them and a chronological timeline of every change - creation, status, priority, description, and all custom-field updates including assignee.

Two improvements to the inbuilt issue manager that together answer the most common 'who did this?' questions without leaving the issue.

- 'Reported by:' label - The Edit Issue page now shows a read-only 'Reported by:' label at the top (above the Title field) with the author's avatar and full name. Read-only - appears whenever the issue has a recorded creator.
- Activity timeline - A new Activity section on the issue view (always visible) and on the Edit Defect page (collapsible) shows a chronological feed of every change: creation, title, description, status, priority, and all custom-field updates including user-type 'assignee' fields. Each entry shows the actor's avatar, the change in plain language (e.g., set Assigned To to Linda Davis, Changed Status from To Do to In Progress), and a timestamp. The list lazy-loads 20 entries at a time as you scroll.
TCV-6522TCV-6548
UI 143b8f66 !182
API 2ad2dd6e !191
Improvement

Issues Page Defaults to 'Assigned to Me'

The Issues page now opens with a default filter showing only issues assigned to the current user - testers see their work first instead of the full project backlog.

Opening the Issues grid used to drop you into the full project backlog. It now opens pre-filtered to issues assigned to the current user, so testers see 'their' work first.

- Default filter - Assignment is detected via any user-type custom field on the issue whose value matches the current user.
- Clear filters - A 'Clear filters' link appears above the grid whenever any filter is active (matching the pattern on the Test Cases manage page). Clicking it shows all issues for the project.
- Empty state - If you have no assigned issues, an empty-state card reads 'No issues assigned to you' with a 'Clear filter' button.
- Session memory - Clearing is remembered for the rest of the browser session; the default reapplies in a new session, so the 'see my work first' experience persists long-term.
TCV-6521
UI 25442c30 !180
API 9b30da70 !189
Fix

Faster Test Plan Run Page (No More N+1 Step-Progress Fetches)

The Test Plan Run page no longer fires one extra request per unexecuted row to render the step progress ring - the data is now returned in the main grid response.

Opening the Test Plan Run page on a typical 200-row plan used to trigger 150-200 simultaneous network requests just to draw the small step-progress ring next to each unexecuted row's status icon. The fix bakes the step and dataset progress data into the main grid response, eliminating the per-row fetches entirely.

The ring still appears as before for partially-executed cases and dataset-driven cases - the only visible difference is a noticeably faster page load and much less network traffic.
TCV-6560
UI 51a639af !181
API af5eff6c !190
Fix

Fixed Runaway Growth in Test Plan Execution Rows

A field on each execution row was roughly doubling in size with every new run, eventually reaching 16 MB. The fix carries data forward correctly and cleans up rows already affected.

A silent data-corruption bug was causing the validation_data field on each test plan execution row to roughly double in size every time you started a new run of a plan. Over enough runs, individual rows had grown to ~16 MB containing only escaped quotation marks around the literal word 'null' - wasting roughly 1.7 GB of database storage in production and risking eventual save failures.

The fix correctly carries forward genuine validation data across runs without re-encoding it, and a one-time cleanup repairs (or clears) the rows that had already been corrupted. No UI change - the benefit is faster, more reliable test plan runs and reduced storage usage. Affects all customers, not just those actively using the validation feature.
TCV-6555
API df0b7fbf !188
Feature

Public Project Dashboards

Share a project's overview dashboard with anyone via a secure read-only link. No TestCollab account needed for viewers.

Project leads can now share a project dashboard publicly without giving viewers a paid seat or login. Generate a public link from the project overview and send it to stakeholders, customers, or auditors who only need to see status.

- Read-only guest view - Public viewers see the dashboard's pinned reports, recent activity, defect status, and error-prone test cases. All authenticated actions and navigations away from the dashboard are suppressed.
- Token-based access - The link is a signed token bound to the project. Revoke access by toggling the project off public visibility.
TCV-6531
Feature

Configurable Plan Completion Statuses

Choose which test execution statuses count as 'done' for a project. A test plan finishes when every case reaches a status in your chosen set, not just when there are zero unexecuted.

Some teams treat any executed status (Passed, Failed, Skipped, Blocked) as 'done'. Others only consider Passed cases as done and want the plan to stay in progress until everything is green. The new Plan Done Statuses setting in Project Settings lets you pick the statuses that count.

- Project Settings dropdown - Pick one or more active statuses on the General Settings page. Active statuses for the project are auto-loaded; the unexecuted system status is excluded.
- Plan completion uses your set - The 'completed' check on the run summary, the 'Run now' prompt on the test plan view, and the regression API's 'unfinished run' guard all switch from unexecuted == 0 to a check against your configured done statuses.
TCV-6525TCV-6543TCV-6550TCV-6551TCV-6552
Improvement

QA Copilot: Spreadsheet Uploads for Requirement-Based Generation

QA Copilot's 'requirements text' source now accepts CSV, XLSX, and ODS files alongside PDFs. Drop in a feature spec spreadsheet and Copilot generates test cases from each row.

When generating test cases from requirements, you can now upload a spreadsheet (CSV, XLS, XLSX, ODS) instead of pasting text or attaching a PDF. This is useful for teams that maintain feature specs, story lists, or acceptance criteria in a tabular format.

- Supported formats - CSV, XLS, XLSX, and ODS files. Up to 3 sheets per workbook, 10 rows per sheet, and 12 columns per sheet are read as context.
Improvement

Step Progress Ring on Test Run Status

Test plan run cards now show a small ring visualizing per-step pass/fail/skip/block status alongside the overall test case status.

Inside a running test plan, the status icon next to each test case now expands into a step progress ring when step-level results are available. At a glance you can see how many steps passed, failed, were skipped, or blocked, which makes it easy to spot cases that 'failed but mostly worked' or 'passed but skipped half the steps'.
Feature

Issue ↔ Test Case Traceability for Inbuilt Defects

The inbuilt defect manager now surfaces every test case linked to an issue, both as a grid column and on the issue detail page.

Inbuilt issues already linked to test cases through manual linking and through automatic links created when a defect is filed from a failed run, but the relationship wasn't visible in the issue manager. This release surfaces it everywhere.

- 'Test Cases' column in the issues grid shows comma-separated, clickable test case IDs for each issue. Filter the grid by test case ID to find issues by the cases they cover.
- 'Linked Test Cases' section on the issue detail page lists each linked case with its title, ID, and any custom fields.
- CSV export of issues now includes a 'Linked Test Cases' column.

Applies to projects using the inbuilt defect manager. External issue trackers (Jira, GitHub, GitLab, Azure DevOps, ClickUp) are out of scope for this release.
TCV-6547
Fix

Performance Fixes for Large Test Plans

Two memory hotfixes for projects with very large test plans: queue-result persistence after run creation and the latest-records lookup on the executed test case API.

Customers with test plans containing tens of thousands of executed test cases were hitting Node out-of-memory crashes on two paths. Both have been fixed with bounded queries.

- TestPlanRunAfterCreate no longer loads the entire queue results payload into memory when persisting a new run.
- executedtestcase.getLatestRecords now uses a bounded query so large plans don't blow up the API process.
Improvement

Issues CSV Export Includes Time and Company Timezone

The issues CSV export now writes timestamps in your company's configured timezone and includes the time component, not just the date.

Previously, dates in the issues CSV export were date-only and rendered in UTC, which made it harder to correlate issue activity with audit logs from other systems. The export now includes time and is formatted using the company's timezone setting.
TCV-6524
Feature

Defect Notifications V2 and Defect/Issue Export

Email notifications for assignees on user-type custom fields, status-change emails on inbuilt issues, and CSV export for both defects and inbuilt issues with column selection.

Two improvements to the inbuilt defect manager:

- Assignee notifications via custom fields - When an issue is created with a user assigned through any user-type custom field, the assignee receives an email notification. When the issue's status changes, the assignee is notified again.
- CSV export for defects and issues - Export filtered or selected defects and issues to CSV with a column picker, available from the new Export button on the defects and issues grids.
TCV-6513TCV-6514
Fix

Bug Fixes & Stability Improvements

Fixes for custom report category limits, linked issue deletion, test case error messages and tag handling, and grid drag-drop in test plan execution.

This release rolls up several stability fixes:

- Custom report categories - The maximum number of categories per dimension was raised from 25 to 100 so reports with high-cardinality groupings render correctly.
- Linked issue deletion - Deleting a linked issue no longer fails when defect records reference it; the related defect rows are cleaned up first.
- Test case error messages - Database errors during test case save are sanitized so internal SQL details no longer leak into user-facing error toasts.
- Test case tag handling - Null entries in test case tag arrays are filtered out instead of causing 'undefined binding' errors during create or update.
- Test case grid drag-drop - Drag-drop reordering in the test case grid no longer crashes when the over-row is missing data, and respects the 'can run' permission in test plan execution mode.
TCV-6473TCV-6483TCV-6498TCV-6499
Feature

tc-cli: Zero-Setup CI Reporting with `--auto-create`

Upload test results to TestCollab from CI with no manual setup. The new `--auto-create` flag on `tc report` creates the tag, suites, test cases, folder, and test plan automatically from your result file.

Getting test results into TestCollab used to require pre-creating a test plan and tagging test cases. The new --auto-create flag on tc report removes all that setup.
tc report --project 123 --format junit --result-file results.xml --auto-create
- Auto-creates everything missing: Tag (CI Imported), test suites (humanized from classname/describe blocks), test cases, the CI test plan folder, and a fresh test plan named CI Run: DD-MM-YYYY HH:MM.
- Smart matching: Tests with TC IDs (e.g. [TC-42]) match by ID. Tests without IDs match by normalized title within the same suite. No match? A new test case is created.
- Mixed mode: Some tests can have IDs while others rely on title matching. Both work in the same result file.
- Suite name humanization: Raw test runner names like com.app.LoginTests, tests/auth/login.spec.ts, or UserProfileTests are automatically cleaned up into readable suite titles.
- Reuses on subsequent runs: The tag, suites, folder, and test cases are reused on every run, so only a new test plan is created each time.

Works with both JUnit XML and Mochawesome JSON. See the auto-create docs for permission requirements and CI examples.
Feature

Project Secrets: Secure Variables for Test Data

Store API keys, passwords, and tokens as encrypted project-level secrets and reference them in test steps with {{secrets.NAME}} syntax.

Test steps often need sensitive data - API keys, auth tokens, database passwords. Hardcoding them in test cases is a security risk. Project Secrets lets you store sensitive values with AES-256 encryption and reference them in any test step using {{secrets.NAME}} syntax.

- Encrypted storage: Secrets are encrypted at rest. Only users with the reveal permission can view the actual value.
- RBAC controls: Manage who can create, edit, reveal, and delete secrets through role permissions.
- Use anywhere in test steps: Reference secrets with {{secrets.API_KEY}} in step descriptions or expected results. Values resolve at execution time.

Read more →
TCV-6397
Improvement

QA Copilot: Redesigned Proposals & One-Click Automation

The QA Copilot proposals page has been redesigned with a cleaner layout, setup modal, and automation status tracking for accepted test cases.

The QA Copilot proposals experience has been significantly improved:

- Redesigned proposals UI: Cleaner layout with better badge styling, tab sizing, and spacing.
- Setup modal: Configure QA Copilot directly from the proposals page with a guided setup flow.
- Automation status tracking: Accepted test cases now show their automation status (Not Automated, In Progress, Automated) with color-coded pills.
- Automate button: One-click automation trigger on accepted test cases with status-aware labels.
TCV-6444TCV-6445TCV-6447TCV-6452
Feature

Pinned Report Widgets & Release Test Plan Selection

Pin your most-used reports to the project dashboard and link specific test plans to releases.

Two quality-of-life improvements for project management:

- Pinned report widgets: Pin your most important reports directly to the project overview dashboard for at-a-glance visibility. No more navigating to the reports page for your daily metrics.
- Test plan selection for releases: When creating or editing a release, you can now select which test plans are included. This gives you finer control over which execution data feeds into the release readiness dashboard.
TCV-3720TCV-6441
Fix

Bug Fixes & Stability Improvements

Fixes for defect severity labels, dataset handling on test case reverts, traceability matrix improvements, and service worker caching.

This release includes several bug fixes and stability improvements across the platform, including fixes for defect severity defaults, stale dataset handling during test case reverts, release readiness calculations, and service worker cache reliability.
TCV-6360TCV-6409TCV-6429TCV-6432TCV-6434TCV-6472TCV-6474
Feature

AI Test Case Generation from Jira Requirements

Generate test cases directly from Jira user stories with per-requirement traceability and context-aware AI.

Generate test cases from Jira requirements with QA Copilot
QA Copilot now generates test cases from your synced Jira requirements. Connect your Jira instance, select up to 5 user stories, and let AI generate structured test cases with steps and expected results - automatically linked to their source requirement.

Read more →
TCV-6413TCV-6416TCV-6410TCV-6421
Feature

Jira Forge App 2.0: Test Management Inside Jira

The TestCollab Jira app has been completely rebuilt on Atlassian's Forge platform - faster, more secure, and natively integrated into every Jira issue, project, and admin page.

Version 2.0 of the TestCollab Jira app is now live on the Atlassian Marketplace. This is a ground-up rebuild on Forge, replacing the previous Connect-based architecture.

- Issue panel & activity tab: View, add, edit, and link test cases directly on any Jira issue. Configure placement per project (sidebar panel or activity tab).
- Test plan management: Create test plans, assign testers, and track execution progress without leaving Jira.
- One-click defect pushing: Failed test? Push a bug to Jira in one click with automatic bidirectional linking.
- Requirements traceability: Link user stories and epics as requirements and generate traceability matrices for coverage visibility.
- Project dashboard: Each Jira project gets a dedicated TestCollab page with suites, recent executions, and coverage metrics.
- Project-level settings: Project admins can configure the TestCollab connection from project settings (no Jira admin access needed).
- Global admin page: Manage the TestCollab connection and control which projects have the integration enabled.
- Free: No charge on the Atlassian Marketplace.

Read more →
Improvement

MCP Server: Suites, Test Plans & Simplified Setup

The MCP server now supports test suites, test plans, and smart context loading - and connects via npx with zero hosted infrastructure.

The TestCollab MCP server has been updated with new capabilities and a simplified connection method.

- Test suite management: Create, list, update, delete, move, and reorder test suites directly from your AI assistant.
- Test plan management: Create, list, update, and delete test plans with configurations and tester assignments.
- Smart context loading: A new project context tool loads suites, tags, users, and custom fields upfront so you can reference everything by name instead of numeric ID.
- Simplified setup: The server now runs locally via npx @testcollab/mcp-server with environment variable authentication. The previous hosted HTTP endpoint (mcp.testcollab.com) has been deprecated.

See the MCP Server integration page for setup instructions and the full list of 17 available tools.
Improvement

CLI Renamed to @testcollab/cli & JUnit XML Support

The TestCollab CLI is now published as a scoped npm package (@testcollab/cli) with npm provenance, and adds native JUnit XML report support alongside Mochawesome.

Two updates to the TestCollab CLI:

- Package renamed to @testcollab/cli: The CLI has moved from testcollab-cli to the scoped @testcollab/cli package on npm. The new package includes npm provenance so you can verify every published build traces back to its GitHub Actions workflow. Update your install commands and CI pipelines:
npm install -g @testcollab/cli
- JUnit XML report support: The tc report command now accepts JUnit XML files in addition to Mochawesome JSON. This means test results from Java (JUnit, TestNG, Maven Surefire), Python (pytest), C# (NUnit, xUnit), .NET, and most other frameworks that output JUnit XML can now be uploaded directly - no format conversion needed:
tc report --project 42 --test-plan-id 100 --format junit --result-file ./test-results/junit.xml


The old testcollab-cli package is deprecated. All existing commands and flags work the same way under the new package name.
Feature

Release Readiness Dashboard & Defect Status Sync

A live GO/NO-GO dashboard for every release, plus automatic defect status sync from your issue manager.

Release readiness dashboard showing GO verdict, pass rate, open defects, evidence coverage, and release comparison
Two new capabilities for release management:

- Release readiness dashboard: Every release now has a readiness page showing a computed GO/NO-GO verdict based on configurable thresholds. See pass rate, open defect count, evidence coverage, execution progress, coverage breakdowns by suite/environment/configuration, and a comparison against the previous release - all computed live from your test plan data
- Defect status sync: Defect statuses now sync automatically from your connected issue manager (Jira, GitLab, Azure DevOps, GitHub, ClickUp). When a bug moves to Resolved or Closed in your tracker, the status updates in TestCollab and the release readiness verdict recalculates immediately
- Defects filtered by release: Click "View All Defects" from the readiness dashboard to jump to the defects page pre-filtered to that release. A banner shows the active filter and can be cleared with one click

Read more →
Feature

External Email Notifications, ClickUp Integration & More

Notify external stakeholders via email without adding seats, file bugs to ClickUp, exclude test cases per config, and reassign reviewers.

This release brings several new capabilities:

- External email notifications: Add up to 10 external email addresses per project to automatically receive test plan status updates when a plan finishes, is delayed, or approaches its deadline. Recipients get a summary with a public link to drill into details - no account or paid seat required. Read the announcement →
- ClickUp integration: ClickUp is now available as a bug tracker alongside Jira, GitLab, Azure DevOps, and GitHub. File defects directly from failed test executions with streamlined field mapping
- Config-level test case exclusion: Remove individual test cases from specific configurations in a test plan. Execution counts and progress stats automatically adjust per configuration
- Reassign test case reviewer: Change the assigned reviewer on a pending review. Both the old and new reviewer are notified, and the change is logged in the review trail
API 2b30fcfe !168
UI c7068c12 !164
Improvement

Failed Click Detection

QA Copilot now detects when a click has no effect, preventing false-positive test results.

Pixel-diff comparison showing no-op interaction detection
QA Copilot's AI test engine received several core improvements:

- No-op interaction detection - Uses pixel-diff comparison to detect when a click or action has no visual effect on the page. When no change is detected, assertion retries are disabled, preventing the AI from "self-healing" into a false positive
- Smarter step boundaries - The AI reasoning engine now looks ahead at the next test step to determine whether to perform additional actions (e.g., clicking submit) or stop. This prevents both under-execution and over-execution of test steps
- Improved element confidence - When an instruction references an element by name but no matching element exists in the HTML, the AI now correctly returns low confidence instead of guessing, allowing visual fallback strategies to take over
- Negative test case support - The evaluation framework now supports expected-fail test cases, making it easier to validate that the engine correctly catches real bugs
AI 14a46bf0 !6
Improvement

QA Copilot Training Fixes

Improved AI test generation accuracy for complex UI patterns like row-scoped dropdowns and list interactions.

QA Copilot now handles complex UI patterns more reliably:

- List and table interactions - Correctly targets elements within specific rows, such as clicking a dropdown next to a particular user's email
- Smarter step completion - The AI now finishes each test step precisely as described without performing extra unintended actions
- Better page understanding - Improved ability to identify the right interactive elements on dense, content-heavy pages
AI 2d28caed !5
Feature

Screen Recording for Test Execution

Record your screen while executing tests to capture visual evidence of bugs and test results.

Screen recording indicator on test execution interface
You can now record your screen during test plan execution. Recordings are automatically saved as attachments to each executed test case.

- Enable per project in Project Settings with a simple toggle
- Optional audio capture for narrating your test steps
- Auto-transitions - recording seamlessly moves to the next test case as you navigate
- Recordings are saved as WebM files and attached to the executed test case for easy review
UI fd86f12c !160
Feature

Custom Reports and ServiceNow Integration

Added custom reports for test execution data and ServiceNow integration support

UI e30d2af8 !159
API cad9efc7 !164
Fix

Fixed Test Execution Notification

Fixed crash in test case execution notification system

API 86c2c100 !165
Feature

MCP Server for AI-Assisted Test Management

Connect AI coding assistants like Claude Code, Cursor, and Codex to TestCollab via the Model Context Protocol. Create, query, and update test cases without leaving your IDE.

AI assistant conversation showing test case operations via MCP
We've released an open-source MCP Server that lets AI assistants manage test cases directly. The server supports:

- list_test_cases – Query test cases with filtering, sorting, and pagination
- create_test_case – Create test cases with steps, custom fields, and tags
- update_test_case – Update existing test cases

Works with any MCP-compatible client including Claude Code, Cursor, Windsurf, and OpenAI Codex. Available as a hosted endpoint or self-hosted via GitHub.
Fix

Boldface Tool On Rich Text Boxes Do Not Work

TCV-5913
UI df48c91b !158
Feature

Added QA Copilot Proposed Test Cases

Automatically generate and manage proposed test cases using AI-powered QA Copilot functionality.

API 5614eb17 !163
Improvement

MySQL Database Migration

Enhanced database migration system with MySQL upgrade support and stepwise execution

API 6685e3e4 !161
Feature

Added Linear Integration

Added Linear project management platform to available integrations list

API ab580290 !159
Fix

Fixed Test Plan Run Automation

Fixed automation trigger and data handling issues in test plan run creation workflow.

API 49cf1d34 !157
API 838e3679 !156
API eaed7bd7 !155
Fix

Fixed Onboarding Nudge Timing

Resolved timing calculation issues in onboarding nudge delivery system.

API 6e7e39a4 !154
Improvement

Added Empty States UI

Added empty state illustrations and components for defects, reusable steps, test cases, and tags pages.

UI ad52db01 !153
API d95f9261 !153
Fix

Fixed Onboarding Nudge Service

Resolved issues in onboarding nudge service functionality

API ff09eb62 !152
Fix

Fixed BDD Background Processing

Fixed BDD feature background array processing and error handling in test suite creation

API 4e00eae6 !151
Fix

Fixed Training URL Validation

Fixed URL validation regex pattern for training URLs in QAC functionality

UI f6e5945b !149
Feature

Nudge System & Company Goals

Added onboarding nudge delivery system and company goal tracking functionality.

API 3503db39 !149
UI 4aee9466 !148
Improvement

Enhanced Unsubscribe Flow

Added feedback collection for unsubscribe process and improved email validation messaging

UI b1bb0fa4 !146
Fix

QAC UI Fix

TCV-5994
UI 4988f6c2 !145
Feature

Added Sample Project Flag

Projects can now be marked as sample projects with new is_sample field

API 8d389a43 !148
Fix

Issue With Users Count When Qa Copilot Is Enabled For A Company

TCV-5988
API 8c553f81 !147
Feature

Added Newsletter System

Introduced automated newsletter generation and delivery functionality with weekly preview capabilities.

UI da8bc67b !144
API 04649451 !146
Feature

Added Sample Project Preview

Added modal to preview sample project during company setup process.

UI 7adfaee6 !143
Fix

We Have Stopped Showing Title On The Full Screen View Of Test Case

TCV-5920
UI cce736a6 !142
Feature

Added Real-time Notifications

Added Ably integration for real-time test execution notifications and project sample data creation.

API f42f4c03 !145
Feature

Added TC API

Integrated new TC API functionality for enhanced system capabilities.

API 979204e7
Improvement

Optimized Service Performance

Improved string replacement operations and enhanced debugging for better system performance

API f872612f !144
UI 0529926f !141
API 61040675 !143
Feature

Distributed Cron Locking System

Added distributed locking mechanism to prevent concurrent cron job execution conflicts

API d5229a04 !142
Improvement

Test Case Management Updates

Enhanced test case handling, requirements processing, and user interface components

UI a7c66a28 !140
API c67de10e !141
Fix

It Does Not Allow Me To Invite New Users Even If I Have Lesser Number Of Users Added To Trial Account

TCV-5826
API 2536ffff !140
UI c21d84c7 !139
API 6c44f82d !139
Improvement

Enhanced API Performance & UI Updates

Optimized database queries and added bulk test case review functionality for better performance.

UI 3ca11044 !138
API 819ac096 !138
Improvement

Updated Service and Logging

Enhanced linked project queries, request logging, and deployment configuration

API b04a0d48 !137
Fix

Users Are Not Able To Add Comments To Test Cases On Test Cases Manage Page Or Test Plan Test Cases List Page

TCV-5807
UI 14d19c84 !137
Feature

Added Request Logging and CloudWatch

New middleware for request logging with CloudWatch integration and enhanced project management capabilities

API e5f6a1a6 !136
Feature

Added BDD Sync & Execution Timer

Introduced BDD synchronization endpoints and test execution timing functionality

UI 1b7b1643 !136
API 6d1a5264 !135
Improvement

Removed QAC Banner

Cleaned up header component by removing QAC banner display functionality.

UI 90fb057a !135
Improvement

Enhanced Company Access Controls

Improved user access validation and company scoping across API services and UI components.

UI f8ba6fab !134
UI 86f384e0 !133
API 88ff7c69 !134
Fix

Requirements Traceability Matrix Is Not Being Shown

TCV-5196
UI 3264a7cd !132
API dd9306c3 !133
Feature

Status Management API

Added new status API endpoints and removed deprecated UI components for cleaner codebase

API d33bcc55 !132
UI d588a72b !131