qmetry_update_issue

Update an existing QMetry issue by DefectId and/or entityKey. Parameters: - DefectId (number) *required*: ID of the defect/issue to be updated - entityKey (string): Entity Key of the defect/issue to be updated - issueType (number): Issue type ID (e.g. Bug, Enhancement, etc.) - issuePriority (number): Issue priority ID (e.g. High, Medium, Low, etc.) - summary (string): Summary or title of the defect/issue - description (string): Detailed description of the defect/issue - issueOwner (number): Owner/user ID for the issue - affectedRelease (number): Release IDs affected by this issue - affectedCycles (number): Cycle IDs affected by this issue Output Description: JSON object with update status and details. Use Cases: 1. Update issue summary (title) 2. Change issue priority, type, or owner 3. Update affected release or cycles 4. Update description or environment 5. Bulk update using DefectId and/or entityKey Examples: 1. Update issue summary json { "DefectId": 118150, "summary": "Money withdrawal is success even if insufficient amount_updated" } Expected Output: Issue summary updated successfully. 2. Update issue priority json { "DefectId": 118150, "issuePriority": 189340 } Expected Output: Issue priority updated successfully. 3. Update issue type json { "DefectId": 118150, "issueType": 189337 } Expected Output: Issue type updated successfully. 4. Update affected release json { "DefectId": 118150, "affectedRelease": 3730 } Expected Output: Affected release updated successfully. Hints: 1. To get the DefectId, call the Issue/Fetch issue tool and use data[<index>].id from the response. 2. if you have pass issue key (VT-IS-5, MAC-IS-10 etc.) then first fetch issue by issue key to get issue id. 3. Along with DefectId, pass only those fields which are to be updated. 4. Refer to the Create Issue tool for valid field mappings and values. 5. You can update summary, priority, type, affectedRelease, affectedCycles, description, sync_with, issueOwner, component, environment, tcRunID, etc. 6. If you provide entityKey, it will be used for additional validation but DefectId is required. It is categorised as a Write tool in the SmartBear MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

qmetry_update_issue accepts 9 parameters: summary, DefectId, entityKey, issueType, issueOwner, description, issuePriority, affectedCycles, affectedRelease. Required: DefectId. The full parameter table on this page comes from the server's own tool schema.

Register the SmartBear MCP server in PolicyLayer and add a rule for qmetry_update_issue: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches SmartBear MCP. Nothing to install.

qmetry_update_issue is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Yes. Add a rate_limit block to the qmetry_update_issue rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

Set action: deny in the PolicyLayer policy for qmetry_update_issue. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

qmetry_update_issue is provided by the SmartBear MCP server (SmartBear/smartbear-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.