Remove selected Jira requirements from a QTM4J test cycle by requirement keys, or clear all links at once to repopulate the cycle.
MIT
650,501 tools. Updated 2026-10-13 21:47
"Permission requirements to create and edit issues in Jira using MCP" matching MCP tools:
- Get Jira requirements linked to a test case by its key. Use it to audit traceability, verify coverage, and retrieve requirement keys for release readiness.MIT
- Get the Jira requirements (stories, bugs) linked to a QTM4J test cycle using its key. Enables traceability, coverage checks, and release readiness verification.MIT
- Link test cases to a Jira requirement using test case keys or filter criteria, enabling traceability between Jira requirements and QTM4J test cases.MIT
- Link Jira requirements to a QTM4J test case using requirement keys or a JQL filter, enabling traceability between requirements and test cases.MIT
- Link Jira requirements to a QTM4J test cycle using requirement keys or a JQL filter. Build traceability by associating selected requirements with a cycle, with warnings for unresolved items.MIT
Matching MCP Servers
- FlicenseAqualityDmaintenanceEnables secure file system operations (read, write, delete) and simulated command execution with server-enforced permission policies, risk assessment, and human-in-the-loop approval.5-
- AlicenseAqualityNot gradedmaintenanceEnables AI assistants to interact with Atlassian Jira Cloud, allowing users to manage projects, issues, comments, and workflows through natural language commands.651 npm3-
Matching MCP Connectors
Jira MCP Pack
Visa Requirements MCP — passport visa rules for any nationality → destination pair
- Search Jira issues with JQL to find matching tickets and return key summary fields. Use it for filtered lists instead of fetching a single issue's full details.Apache 2.0
- Get current status and details for external issues from Jira, Linear, Asana, monday.com, or GitHub using their issue IDs. Use it to verify whether issues filed via TestDino are open or resolved.MIT
- Diagnose 401 errors and permission issues by verifying PactFlow AI entitlements and credit balance to resolve access problems.MIT
- Retrieve Jira issues by project or JQL query. Get customized issue lists with configurable result limits.MIT
- Manage Perforce streams: create, update, delete, edit specs, and propagate changes between streams via copy, merge, integrate, or populate.MIT
- Create or update Jira site configuration in FOSSA, enabling issue tracking integration. Configure credentials, fields, and project mappings to align Jira with FOSSA.Apache 2.0
- List all permission schemes in a Jira instance, returning scheme IDs, names, and descriptions.MIT
- Transforms TASKS.md into work items for GitHub, Jira, or Azure Boards, preserving REQ traceability and subtask structure.MIT
- Bulk-create multiple JIRA issues and add dependency links between them in one call, using aliases to reference new issue keys. Returns a YAML report of per-issue and per-link outcomes for targeted retries.BSD 3-Clause
- Search Jira issues with a JQL query or combine project, assignee, and status filters; returns matching issues as YAML.BSD 3-Clause
- Check server permissions to determine allowed operations (create, edit, move, delete) and access mode (read-only or full) before performing filesystem actions.-
- Create multiple Jira issues at once (max 50) by specifying project key, issue type, summary, and optional fields like description, assignee, priority, labels, or custom fields.MIT
- Search Jira work items using JQL queries to find issues by project, status, assignee, priority, or date ranges. Returns matching items with key details for tracking and management.MIT
- Search Jira issues using JQL queries. Find issues by project, status, assignee, or custom criteria, with pagination support.MIT
- Get issues from a Jira Service Desk queue by providing service desk ID and queue ID. Supports pagination with start index and limit.GPL 3.0