Manager 2026.2 Release Notes

February 2026

With Manager 2026.2, we're bringing you a few bugfixes and general improvements to your qTest experience.

Our installation package uploaded February 24 contained an edge-case issue that impacted customers who connect to locally hosted Jira instances. To ensure you get the correct configuration, make sure you download the refreshed qTest installation package uploaded to Support Hub on February 25 (opens in a new tab).

Updated custom test step fields

To give you greater flexibility on what information you include and how you organize your test steps, we've increased the amount of custom fields you can add to 5. That means you can add more specific fields according to your testing needs.

For example, if you want to note how critical a test step's failure would potentially be, you can add a Severity if Fails field. Or, you can add an Input Data Source field that notes where the test data is coming from, whether it's mock data, a spreadsheet, or an API. If you use multiple data sets in your testing, you can add a Data Set field, so your testers know which test data applies to that action.

You can still add custom test step fields the same way you did before, but now you can add even more of them.

Added support for Jira OAuth 2.0

To align with Atlassian's security updates as they deprecate OAuth 1.0a, we've added support for OAuth 2.0 authentication with Jira.

While OAuth 1.0a is still available as an authentication method at the moment, we strongly recommend moving to OAuth 2.0 for the most secure experience, as Atlassian deprecated OAuth 1.0a. You can also continue to authenticate with API tokens for Cloud and Personal Access Tokens for Server or Data Center connections.

We've also added support for shared Jira OAuth 2.0 apps, so different Jira and qTest admins can set up integrations without a single shared admin account.

Learn how to connect your qTest instance with Jira Cloud or Jira Data Center.

API updates

We've added a limit to the /api/v3/projects/{projectId}/search API call, so users can only query a maximum of 200 parameters per request. This is to ensure the API has the memory to process your requests.

Learn more about the qTest API on Swagger (opens in new tab).

Security updates

We made background changes to improve the overall security of qTest Manager.

Removed Firefox plugin

We've deprecated and removed download links for the Firefox qTest plugin from the qTest Integration Browser Plugins section in Download qTest Resources.

To learn more about the deprecation, please refer to our end of support announcement.

To download this plugin for Google Chrome or Microsoft Edge go to our downloads page.

Bug fixes

Ticket #	Component	Description
N/A	qTest - Manager	Improved internal authentication to ensure Support retained applicable login access after OAuth 2.0 updates.
CS0459813	qTest - Manager	Fixed performance issues that occurred when users added test cases in bulk to large projects.
CS0430958	qTest - Manager, qTest - API	Fixed an issue that caused edits to test step custom fields made with the API to interfere with users editing fields in the UI.
CS0447101	qTest - API	Fixed a performance issue that occurred when the `expand=descendants` query parameter was used for large test cycle trees in the `GET /api/v3/projects/{{projectId}}/test-cycles` API call.
CS0456558	qTest - Tosca integration	Fixed an issue where Tosca bulk uploads occasionally delayed or failed to stabilize the bulk upload process.
CS0470332	qTest - Tosca integration	Scheduling a single Tosca test event no longer incorrectly causes qTest to create a duplicate event with one failed execution.
CS0471135	qTest - Jira integration	Fixed an issue that could cause partial or complete failures when users tried to sync a large amount of requirements from Jira to qTest.
CS0444331	qTest - Jira integration	Fixed an issue where test executions in qTest didn't display in the qTest: Test Execution iframe in Jira for linked requirements.
N/A	qTest - Jira integration	Fixed an issue where the Retrieve data button still worked, even if the external Jira integration was disabled.
CS0422061	qTest - Jira integration	Fixed an issue that caused Jira custom fields to incorrectly export as URL-encoded characters, so Jira custom fields now export with readable text.
CS0465083	qTest - Manager	Fixed an issue where the Planned vs Executed report in Insights couldn't pull information for test cycles and test suites in certain situations.
CS0422061	qTest - Jira integration	Fixed an issue that caused custom Jira fields to be URL-encoded when users exported an Excel sheet from Data Query.
CS0465449, CS0464387, CS0469310	qTest - Manager	Fixed an issue that caused all event types to halt processing after the qTest service was restarted.
N/A	qTest - Jira integration	Fixed an issue where the Retrieve data button still functioned for requirements and releases, even if the external requirement or release integration was turned off.
N/A	qTest - Jira integration	Fixed an issue where Jira DC sprints didn't auto-sync with qTest.
CS0456558	qTest - Tosca integration	Fixed a performance issue that occurred when users processed a Tosca bulk upload through the API.
CS0476672	qTest - Vera integration	Fixed an issue that caused Vera system fields to be visible in Requirement Field Settings and Defect Field Settings, even if the Vera integration wasn't enabled.
CS0464387	qTest - Manager	Fixed a memory leak that affected general performance.
N/A	qTest - Manager	Added a redirect to the On-Premises Launch quick start guide for On-Premises users who access the SaaS documentation linked in qTest.