QMetry: Execute Quality Gate Report
qmetry_execute_quality_gate_reportExecute a quality gate report to evaluate project health against gate criteria, with optional scoping by release and cycle for release readiness insights.
Instructions
Execute a quality gate report by forwarding the request to the backend analytics engine and returning the results.
Toolset: AI Agent
Parameters:
projectKey (string): Project key - unique identifier for the project (default: "default")
reportName (string) required: Report name identifier (e.g. 'RR' for Release Readiness).
gateIdentifier (string) required: Gate identifier to execute the report against (e.g. 'GATE1').
projectId (number) required: Numeric project ID for the report scope.
releaseId (number): Optional release ID to scope the report to a specific release.
cycleIds (array): Optional array of cycle IDs to scope the report to specific cycles.
page (number): Optional page number for paginated report results.
limit (number): Maximum number of records to return per page. Defaults to 100 if not specified. (default: 100)
Use Cases: 1. Generate a release readiness report for a specific project, release, and cycle 2. Execute a quality gate assessment to evaluate project health against gate criteria 3. Run a gate report scoped to specific cycles within a release 4. Produce analytics data for quality gate evaluation and decision-making
Examples:
Execute a release readiness report for project 45851, release 90698, cycle 129140
{
"reportName": "RR",
"gateIdentifier": "GATE1",
"projectId": 45851,
"releaseId": 90698,
"cycleIds": [
129140
]
}Expected Output: { "data": [...], "total": 0, "success": true, "page": {} }
Execute a gate report without release/cycle scoping
{
"reportName": "RR",
"gateIdentifier": "GATE1",
"projectId": 45851
}Expected Output: { "data": [...], "total": 0, "success": true, "page": {} }
Hints: 1. REQUIRED: 'reportName' identifies the report type (e.g. 'RR' for Release Readiness). 2. REQUIRED: 'gateIdentifier' identifies which gate to evaluate (e.g. 'GATE1'). 3. REQUIRED: 'projectId' must be a valid numeric project ID. 4. OPTIONAL: 'releaseId' scopes the report to a specific release. 5. OPTIONAL: 'cycleIds' scopes the report to specific test cycles within the release. 6. OPTIONAL: 'page' specifies the page number for paginated report results. 7. OPTIONAL: 'limit' sets the maximum number of records per page (defaults to 100). 8. Call 'Fetch Quality Gate Configuration' first to discover available gates and report parameters. 9. The response is returned exactly as received from the backend — no transformation is applied.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Optional page number for paginated report results. | |
| limit | No | Maximum number of records to return per page. Defaults to 100 if not specified. | |
| cycleIds | No | Optional array of cycle IDs to scope the report to specific cycles. | |
| projectId | Yes | Numeric project ID for the report scope. | |
| releaseId | No | Optional release ID to scope the report to a specific release. | |
| projectKey | No | Project key - unique identifier for the project | default |
| reportName | Yes | Report name identifier (e.g. 'RR' for Release Readiness). | |
| gateIdentifier | Yes | Gate identifier to execute the report against (e.g. 'GATE1'). |