QMetry Insights – Admin Control for Jira/Azure Custom Fields (QMetry v8.25)
Starting with QMetry v8.25, system administrators have greater control over which Jira or Azure custom fields are available in QMetry Insights Visual and Advanced Query Reports. This update introduces a more structured way to manage reporting fields, helping teams avoid unnecessary data synchronization and improving overall reporting reliability. What’s Changed Earlier, all Jira or Azure custom fields were automatically available for reporting in Advanced Query Reports. In environments with a large number of custom fields, this could lead to unnecessary synchronization and additional load on the reporting database. With QMetry v8.25, administrators can now explicitly decide which custom fields should be synchronized and used for reporting. Key Highlights Admin-controlled field availability - Only the custom fields explicitly selected by the System Administrator will be synchronized and made available for Custom Reporting. Configuration available under Integrations - A new configuration option is available under Integrations, allowing administrators to choose which Jira or Azure custom fields should be enabled for reporting. Improved reporting performance and reliability - By syncing only the required fields, the system reduces unnecessary data synchronization and improves the stability of the Custom Reporting database. Smooth transition for existing customers - For existing environments, any Jira or Azure custom fields that are already being used in Custom Gadgets will be automatically enabled to ensure that current reports continue to work without interruption. All other fields will remain disabled by default. Why This Change Matters Large Jira and Azure environments often contain hundreds of custom fields, many of which are not needed for reporting. This enhancement helps administrators: Reduce reporting database overhead Improve synchronization efficiency Maintain better control over reporting data Summary The Admin Control for Jira/Azure Custom Fields feature gives administrators the ability to manage reporting fields more effectively while ensuring existing reports remain unaffected. By enabling only the required fields, teams can maintain cleaner data synchronization and more reliable reporting within QMetry Insights.
QMetry MCP: Bringing Control, Coverage, and Traceability to AI-Driven QA
As AI automates more QA work, it becomes harder to track what it creates and runs across tools. QMetry addresses this by providing the control and observability needed to keep AI assisted and AI-driven test management aligned with requirements, execution, and release decisions. This foundation becomes increasingly important as QA workflows grow more automated and distributed across tools. Through the QMetry MCP server, users can interact with QMetry, Jira, and GitHub to generate tests, organize execution, and maintain traceability through simple prompts, without jumping between tools or doing manual linking. These workflows can be triggered from MCP compatible clients such as IDEs or tools like Claude Desktop, while QMetry ensures that all test assets, results, and relationships remain visible, controlled, and auditable. What the QMetry MCP server enables in practice The QMetry MCP server exposes core QMetry test management capabilities as MCP tools. This allows AI assistants to interact with QMetry programmatically, using the same permissions and project context as a human user. Instead of AI generating artifacts in isolation, test cases, execution data, and their relationships are created and maintained directly in QMetry, as part of an AI-driven test management platform. In practice, this unlocks a wide range of QA use cases. Here are a few examples of what teams can do with QMetry MCP: Turn requirements into executable tests AI assistants can fetch epics or stories with acceptance criteria from Jira and generate test cases directly in QMetry, including detailed steps and expected outcomes. These test cases are automatically linked back to their requirements and can be immediately planned for execution. This reduces manual test authoring while ensuring coverage remains visible and traceable. Automate test planning, execution, and defect creation Once test cases exist, the QMetry MCP servercan organize them into test suites based on release cycle and platform, track execution results, and update statuses in bulk. When tests fail, defects can be created in Jira and linked back to the failed executions and original requirements, keeping QA and development workflows connected without manual handoffs. Understand test coverage based on code changes The QMetry MCP server can also support workflows that start from code. By analyzing GitHub commits or pull requests, MCP can identify the related ticket IDs, validate whether those requirements exist in QMetry, and check if they already have test coverage. If gaps are found, teams can address missing coverage before testing or release activities begin. Plan regression testing based on impact Rather than relying on static or overly broad regression suites, MCP driven workflows can help identify which areas of the system are affected by recent changes. Existing test cases can be reused where possible, and relevant test suites can be created or recommended, helping teams focus regression testing where risk is highest. Get end to end traceability and release visibility Because all test cases, executions, and defects are created and linked through the QMetry MCP server, traceability is established as part of the workflow, not as a separate reporting step. Teams can review coverage, execution status, and outstanding defects in context and use this information to assess release readiness without manually stitching data across tools. As AI accelerates the speed of test creation and execution, QMetry becomes the critical layer that keeps everything connected and controlled. It doesn’t just manage tests, it ensures visibility, traceability, and governance across an increasingly distributed, AI-driven QA landscape. With the QMetry MCP server, teams can leverage this functionality directly from the tools they already use, without switching contexts, making QMetry not only the system of record, but the backbone of modern, AI-powered test management. Learn more and started with SmartBear MCP server. See it in action See a couple of short demos that showcase what the QMetry MCP server can unlock in real QA workflows. We’re rapidly expanding MCP driven use cases and unlocking new ways to automate more of the testing lifecycle, while keeping everything visible and traceable in QMetry. Demo 1: Requirements-to-execution traceability Example: Using the QMetry MCP server to turn Jira requirements into executable tests with end-to-end traceability A QA team can pull an epic from Jira, generate detailed test cases in QMetry, automatically link them to the synced requirement, and organize them into a release and platform specific test suite ready for execution. The output is a complete execution and traceability view, showing test status and linked defects in context across the epic, requirement, test cases, suite, executions, and Jira bugs, without manual linking or cross-tool stitching. Demo 2: Release health and readiness Example: Using the QMetry MCP server to generate a release health and readiness report A QA manager can automatically validate release readiness against predefined quality gates, including planned scope completion, test coverage, test execution status, defect severity, and automation results. The output is a clear release decision, supported by full traceability across Jira, test cases, executions, and defects, all exportable into a shareable report. Try out QMetry today or sign up for a quick demo to see more MCP use cases.