jira-automationlisted

# Jira Automation via Rube MCP Automate Jira operations through Composio's Jira toolkit via Rube MCP. ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) - Active Jira connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `jira` - Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas ## Setup **Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. 1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds 2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `jira` 3. If connection is not ACTIVE, follow the returned auth link to complete Jira OAuth 4. Confirm connection status shows ACTIVE before running any workflows ## Core Workflows ### 1. Search and Filter Issues **When to use**: User wants to find issues using JQL or browse project issues **Tool sequence**: 1. `JIRA_SEARCH_FOR_ISSUES_USING_JQL_POST` - Search with JQL query [Required] 2. `JIRA_GET_ISSUE` - Get full details of a specific issue [Optional] **Key parameters**: - `jql`: JQL query string (e.g., `project = PROJ AND status = "In Progress"`) - `maxResults`: Max results per page (default 50, max 100) - `startAt`: Pagination offset - `fields`: Array of field names to return - `issueIdOrKey`: Issue key like 'PROJ-123' for GET_ISSUE **Pitfalls**: - JQL field names are case-sensitive and must match Jira configuration - Custom fields use IDs like `customfield_10001`, not