name: jira-automation
description: "Automate Jira tasks via Rube MCP (Composio): issues, projects, sprints, boards, comments, users. Always search tools first for current schemas."
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.
- Verify Rube MCP is available by confirming
RUBE_SEARCH_TOOLS responds
- Call
RUBE_MANAGE_CONNECTIONS with toolkit jira
- If connection is not ACTIVE, follow the returned auth link to complete Jira OAuth
- 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:
JIRA_SEARCH_FOR_ISSUES_USING_JQL_POST - Search with JQL query [Required]
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 display names
- Results are paginated; check
total vs startAt + maxResults to continue
2. Create and Edit Issues
When to use: User wants to create new issues or update existing ones
Tool sequence:
JIRA_GET_ALL_PROJECTS - List projects to find project key [Prerequisite]
JIRA_GET_FIELDS - Get available fields and their IDs [Prerequisite]
JIRA_CREATE_ISSUE - Create a new issue [Required]
JIRA_EDIT_ISSUE - Update fields on an existing issue [Optional]
JIRA_ASSIGN_ISSUE - Assign issue to a user [Optional]
Key parameters:
project: Project key (e.g., 'PROJ')
issuetype: Issue type name (e.g., 'Bug', 'Story', 'Task')
summary: Issue title
description: Issue description (Atlassian Document Format or plain text)
issueIdOrKey: Issue key for edits
Pitfalls:
- Issue types and required fields vary by project; use GET_FIELDS to check
- Custom fields require exact field IDs, not display names
- Description may need Atlassian Document Format (ADF) for rich content
3. Manage Sprints and Boards
When to use: User wants to work with agile boards, sprints, and backlogs
Tool sequence:
JIRA_LIST_BOARDS - List all boards [Prerequisite]
JIRA_LIST_SPRINTS - List sprints for a board [Required]
JIRA_MOVE_ISSUE_TO_SPRINT - Move issue to a sprint [Optional]
JIRA_CREATE_SPRINT - Create a new sprint [Optional]
Key parameters:
boardId: Board ID from LIST_BOARDS
sprintId: Sprint ID for move operations
name: Sprint name for creation
startDate/endDate: Sprint dates in ISO format
Pitfalls:
- Boards and sprints are specific to Jira Software (not Jira Core)
- Only one sprint can be active at a time per board
4. Manage Comments
When to use: User wants to add or view comments on issues
Tool sequence:
JIRA_LIST_ISSUE_COMMENTS - List existing comments [Optional]
JIRA_ADD_COMMENT - Add a comment to an issue [Required]
Key parameters:
issueIdOrKey: Issue key like 'PROJ-123'
body: Comment body (supports ADF for rich text)
Pitfalls:
- Comments support ADF (Atlassian Document Format) for formatting
- Mentions use account IDs, not usernames
5. Manage Projects and Users
When to use: User wants to list projects, find users, or manage project roles
Tool sequence:
JIRA_GET_ALL_PROJECTS - List all projects [Optional]
JIRA_GET_PROJECT - Get project details [Optional]
JIRA_FIND_USERS / JIRA_GET_ALL_USERS - Search for users [Optional]
JIRA_GET_PROJECT_ROLES - List project roles [Optional]
JIRA_ADD_USERS_TO_PROJECT_ROLE - Add user to role [Optional]
Key parameters:
projectIdOrKey: Project key
query: Search text for FIND_USERS
roleId: Role ID for role operations
Pitfalls:
- User operations use account IDs (not email or display name)
- Project roles differ from global permissions
Common Patterns
JQL Syntax
Common operators:
project = "PROJ" - Filter by project
status = "In Progress" - Filter by status
assignee = currentUser() - Current user's issues
created >= -7d - Created in last 7 days
labels = "bug" - Filter by label
priority = High - Filter by priority
ORDER BY created DESC - Sort results
Combinators:
AND - Both conditions
OR - Either condition
NOT - Negate condition
Pagination
- Use
startAt and maxResults parameters
- Check
total in response to determine remaining pages
- Continue until
startAt + maxResults >= total
Known Pitfalls
Field Names:
- Custom fields use IDs like
customfield_10001
- Use JIRA_GET_FIELDS to discover field IDs and names
- Field names in JQL may differ from API field names
Authentication:
- Jira Cloud uses account IDs, not usernames
- Site URL must be configured correctly in the connection
Quick Reference
| Task |
Tool Slug |
Key Params |
| Search issues (JQL) |
JIRA_SEARCH_FOR_ISSUES_USING_JQL_POST |
jql, maxResults |
| Get issue |
JIRA_GET_ISSUE |
issueIdOrKey |
| Create issue |
JIRA_CREATE_ISSUE |
project, issuetype, summary |
| Edit issue |
JIRA_EDIT_ISSUE |
issueIdOrKey, fields |
| Assign issue |
JIRA_ASSIGN_ISSUE |
issueIdOrKey, accountId |
| Add comment |
JIRA_ADD_COMMENT |
issueIdOrKey, body |
| List comments |
JIRA_LIST_ISSUE_COMMENTS |
issueIdOrKey |
| List projects |
JIRA_GET_ALL_PROJECTS |
(none) |
| Get project |
JIRA_GET_PROJECT |
projectIdOrKey |
| List boards |
JIRA_LIST_BOARDS |
(none) |
| List sprints |
JIRA_LIST_SPRINTS |
boardId |
| Move to sprint |
JIRA_MOVE_ISSUE_TO_SPRINT |
sprintId, issues |
| Create sprint |
JIRA_CREATE_SPRINT |
name, boardId |
| Find users |
JIRA_FIND_USERS |
query |
| Get fields |
JIRA_GET_FIELDS |
(none) |
| List filters |
JIRA_LIST_FILTERS |
(none) |
| Project roles |
JIRA_GET_PROJECT_ROLES |
projectIdOrKey |
| Project versions |
JIRA_GET_PROJECT_VERSIONS |
projectIdOrKey |
1---2name: jira-automation-33description: <!-- AUTO-GENERATED by export-skills.py — DO NOT EDIT -->4---5<!-- AUTO-GENERATED by export-skills.py — DO NOT EDIT -->6---7name: jira-automation8description: "Automate Jira tasks via Rube MCP (Composio): issues, projects, sprints, boards, comments, users. Always search tools first for current schemas."9---1011# Jira Automation via Rube MCP1213Automate Jira operations through Composio's Jira toolkit via Rube MCP.1415## Prerequisites1617- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)18- Active Jira connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `jira`19- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas2021## Setup2223**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.2425261. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds272. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `jira`283. If connection is not ACTIVE, follow the returned auth link to complete Jira OAuth294. Confirm connection status shows ACTIVE before running any workflows3031## Core Workflows3233### 1. Search and Filter Issues3435**When to use**: User wants to find issues using JQL or browse project issues3637**Tool sequence**:381. `JIRA_SEARCH_FOR_ISSUES_USING_JQL_POST` - Search with JQL query [Required]392. `JIRA_GET_ISSUE` - Get full details of a specific issue [Optional]4041**Key parameters**:42- `jql`: JQL query string (e.g., `project = PROJ AND status = "In Progress"`)43- `maxResults`: Max results per page (default 50, max 100)44- `startAt`: Pagination offset45- `fields`: Array of field names to return46- `issueIdOrKey`: Issue key like 'PROJ-123' for GET_ISSUE4748**Pitfalls**:49- JQL field names are case-sensitive and must match Jira configuration50- Custom fields use IDs like `customfield_10001`, not display names51- Results are paginated; check `total` vs `startAt + maxResults` to continue5253### 2. Create and Edit Issues5455**When to use**: User wants to create new issues or update existing ones5657**Tool sequence**:581. `JIRA_GET_ALL_PROJECTS` - List projects to find project key [Prerequisite]592. `JIRA_GET_FIELDS` - Get available fields and their IDs [Prerequisite]603. `JIRA_CREATE_ISSUE` - Create a new issue [Required]614. `JIRA_EDIT_ISSUE` - Update fields on an existing issue [Optional]625. `JIRA_ASSIGN_ISSUE` - Assign issue to a user [Optional]6364**Key parameters**:65- `project`: Project key (e.g., 'PROJ')66- `issuetype`: Issue type name (e.g., 'Bug', 'Story', 'Task')67- `summary`: Issue title68- `description`: Issue description (Atlassian Document Format or plain text)69- `issueIdOrKey`: Issue key for edits7071**Pitfalls**:72- Issue types and required fields vary by project; use GET_FIELDS to check73- Custom fields require exact field IDs, not display names74- Description may need Atlassian Document Format (ADF) for rich content7576### 3. Manage Sprints and Boards7778**When to use**: User wants to work with agile boards, sprints, and backlogs7980**Tool sequence**:811. `JIRA_LIST_BOARDS` - List all boards [Prerequisite]822. `JIRA_LIST_SPRINTS` - List sprints for a board [Required]833. `JIRA_MOVE_ISSUE_TO_SPRINT` - Move issue to a sprint [Optional]844. `JIRA_CREATE_SPRINT` - Create a new sprint [Optional]8586**Key parameters**:87- `boardId`: Board ID from LIST_BOARDS88- `sprintId`: Sprint ID for move operations89- `name`: Sprint name for creation90- `startDate`/`endDate`: Sprint dates in ISO format9192**Pitfalls**:93- Boards and sprints are specific to Jira Software (not Jira Core)94- Only one sprint can be active at a time per board9596### 4. Manage Comments9798**When to use**: User wants to add or view comments on issues99100**Tool sequence**:1011. `JIRA_LIST_ISSUE_COMMENTS` - List existing comments [Optional]1022. `JIRA_ADD_COMMENT` - Add a comment to an issue [Required]103104**Key parameters**:105- `issueIdOrKey`: Issue key like 'PROJ-123'106- `body`: Comment body (supports ADF for rich text)107108**Pitfalls**:109- Comments support ADF (Atlassian Document Format) for formatting110- Mentions use account IDs, not usernames111112### 5. Manage Projects and Users113114**When to use**: User wants to list projects, find users, or manage project roles115116**Tool sequence**:1171. `JIRA_GET_ALL_PROJECTS` - List all projects [Optional]1182. `JIRA_GET_PROJECT` - Get project details [Optional]1193. `JIRA_FIND_USERS` / `JIRA_GET_ALL_USERS` - Search for users [Optional]1204. `JIRA_GET_PROJECT_ROLES` - List project roles [Optional]1215. `JIRA_ADD_USERS_TO_PROJECT_ROLE` - Add user to role [Optional]122123**Key parameters**:124- `projectIdOrKey`: Project key125- `query`: Search text for FIND_USERS126- `roleId`: Role ID for role operations127128**Pitfalls**:129- User operations use account IDs (not email or display name)130- Project roles differ from global permissions131132## Common Patterns133134### JQL Syntax135136**Common operators**:137- `project = "PROJ"` - Filter by project138- `status = "In Progress"` - Filter by status139- `assignee = currentUser()` - Current user's issues140- `created >= -7d` - Created in last 7 days141- `labels = "bug"` - Filter by label142- `priority = High` - Filter by priority143- `ORDER BY created DESC` - Sort results144145**Combinators**:146- `AND` - Both conditions147- `OR` - Either condition148- `NOT` - Negate condition149150### Pagination151152- Use `startAt` and `maxResults` parameters153- Check `total` in response to determine remaining pages154- Continue until `startAt + maxResults >= total`155156## Known Pitfalls157158**Field Names**:159- Custom fields use IDs like `customfield_10001`160- Use JIRA_GET_FIELDS to discover field IDs and names161- Field names in JQL may differ from API field names162163**Authentication**:164- Jira Cloud uses account IDs, not usernames165- Site URL must be configured correctly in the connection166167## Quick Reference168169| Task | Tool Slug | Key Params |170|------|-----------|------------|171| Search issues (JQL) | JIRA_SEARCH_FOR_ISSUES_USING_JQL_POST | jql, maxResults |172| Get issue | JIRA_GET_ISSUE | issueIdOrKey |173| Create issue | JIRA_CREATE_ISSUE | project, issuetype, summary |174| Edit issue | JIRA_EDIT_ISSUE | issueIdOrKey, fields |175| Assign issue | JIRA_ASSIGN_ISSUE | issueIdOrKey, accountId |176| Add comment | JIRA_ADD_COMMENT | issueIdOrKey, body |177| List comments | JIRA_LIST_ISSUE_COMMENTS | issueIdOrKey |178| List projects | JIRA_GET_ALL_PROJECTS | (none) |179| Get project | JIRA_GET_PROJECT | projectIdOrKey |180| List boards | JIRA_LIST_BOARDS | (none) |181| List sprints | JIRA_LIST_SPRINTS | boardId |182| Move to sprint | JIRA_MOVE_ISSUE_TO_SPRINT | sprintId, issues |183| Create sprint | JIRA_CREATE_SPRINT | name, boardId |184| Find users | JIRA_FIND_USERS | query |185| Get fields | JIRA_GET_FIELDS | (none) |186| List filters | JIRA_LIST_FILTERS | (none) |187| Project roles | JIRA_GET_PROJECT_ROLES | projectIdOrKey |188| Project versions | JIRA_GET_PROJECT_VERSIONS | projectIdOrKey |189190<!-- Source: .faos/custom/skills/devops/jira-automation/SKILL.md -->