Connect Your AI Agent with Tricentis qTest for Slack

Update ONE existing requirement in a qTest project. Use List Requirements to find the requirement ID and List Requirement Fields to discover field IDs for the Properties parameter. Name is required by the API on every update — resupply the requirement's current name (from Get Requirement) if you only want to change Properties. This tool has no bulk/mass-update mode — before calling it repeatedly to apply the same change across many requirements, confirm the full scope (which requirements, what change) with the user first; do not sweep an entire project's requirements on a single broad instruction. If you ask for that confirmation and don't receive an explicit yes, STOP — do not call this tool anyway. Proceeding without an actual confirmation is exactly the behavior this warning exists to prevent, even if the original instruction sounded broad enough to imply it. This warning is about scope (which/how many requirements), not about calling this tool at all — a single, already-specific instruction (a named requirement ID and field change) needs no extra confirmation. Example: projectId: 1, requirementId: "101", name: "User can log in", properties: "[{\"field_id\": 3, \"field_value\": \"1\"}]" → returns the updated requirement object. See the documentation

Update an existing defect in a qTest project. Use List Defects to find the defect ID and List Defect Fields to discover field IDs for the Properties parameter. Example: projectId: 1, defectId: "201", properties: "[{\"field_id\": 2, \"field_value\": \"2\"}]" → returns the updated defect object. See the documentation

Submit a new defect in a qTest project. Use List Project ID Options for the project ID and List Defect Fields to discover field IDs and required fields for the Properties parameter. Example: projectId: 1, properties: "[{\"field_id\": 1, \"field_value\": \"Button not clickable\"}, {\"field_id\": 2, \"field_value\": \"1\"}]" → returns {id: 202, properties: [...]}. See the documentation

List requirements in a qTest project. Use this to find requirement IDs to use when getting or updating a specific requirement. If the response contains a full page of results, increment the Page parameter and call again to retrieve the next page. Example: projectId: 1, page: 1 → returns [{id: 101, name: "User can log in"}, {id: 102, name: "Password reset via email"}]. See the documentation

List all available fields for requirements in a qTest project, including field IDs, types, and allowed values. Use this to discover field IDs before creating or updating requirements. Pass fields (e.g. ["id", "label", "required"]) to keep only those attributes per field — some fields' allowed_values lists are long, so omitting them when you only need the field ID/label keeps the response small. Example: projectId: 1 → returns [{id: 3, label: "Priority", attribute_type: "String", allowed_values: [{label: "High", value: "1"}, {label: "Medium", value: "2"}], required: false}]. See the documentation

List all qTest projects accessible to the connected account. Use this to find the Project ID required by all other actions. Example: returns [{label: "Acme QA", value: 1}, {label: "Frontend Suite", value: 2}]. See the documentation.

List all modules in a qTest project, including nested submodules. Use List Project ID Options for the project ID. Use this to find module IDs to use as the Parent ID in Create Requirement. Example: projectId: 1 → returns [{id: 10, name: "Authentication"}, {id: 11, name: "Checkout"}]. See the documentation

List defects in a qTest project updated after a given start time. Use this to find defect IDs to use when getting or updating a specific defect. If the response contains a full page of results, increment the Page parameter and call again for more. Defaults to defects updated in the last 30 days, and includes only the Summary property per defect to keep the response small — projects with long-running defect logs can return large payloads otherwise, since some properties (like Description) may contain lengthy text. Pass fields (e.g. ["Summary", "Status"]) to include different or additional named properties instead. Use Get Defect for a defect's full property set. Example: projectId: 1, startTime: "2026-09-01T00:00:00Z" → returns [{id: 201, properties: [{field_id: 1, field_value: "Login crash"}]}, ...]. See the documentation

List all available fields for defects in a qTest project, including field IDs, types, and allowed values. Use this to discover field IDs before submitting or updating defects. Pass fields (e.g. ["id", "label", "required"]) to keep only those attributes per field — some fields' allowed_values lists are long, so omitting them when you only need the field ID/label keeps the response small. Example: projectId: 1 → returns [{id: 1, label: "Summary", attribute_type: "String", required: true}, {id: 2, label: "Status", attribute_type: "String", allowed_values: [{label: "New", value: "1"}], required: true}]. See the documentation

Get full details of a specific requirement by ID. Use List Requirements to find the requirement ID. Example: projectId: 1, requirementId: "101" → returns {id: 101, name: "User can log in", properties: [{field_id: 3, field_value: "High"}]}. See the documentation

Get full details of a specific defect by ID. Use List Defects to find the defect ID and List Defect Fields to interpret field IDs in the response. Example: projectId: 1, defectId: "201" → returns {id: 201, properties: [{field_id: 1, field_value: "Login crash"}, {field_id: 2, field_value: "New"}]}. See the documentation

Create a new requirement under a parent module in a qTest project. Use List Project ID Options for the project ID, List Modules for the parent module ID, and List Requirement Fields to discover field IDs for the Properties parameter. Example: projectId: 1, parentId: "10", requirementName: "User can reset password", properties: "[{\"field_id\": 3, \"field_value\": \"1\"}]" → returns {id: 103, name: "User can reset password", ...}. See the documentation