jira-assistant

Ask the agent to create a task with a summary, and it uses the createJiraIssue MCP tool with your detected project key and Cloud ID. The description follows a standard template with Context, Objective, Technical Requirements, and Acceptance Criteria sections.

Use the searchJiraIssuesUsingJql tool with queries that always include your project key, such as "project = KAN AND status = In Progress". For general natural language queries, use the Rovo search tool first instead of JQL.

Yes, configuration can be detected from AGENTS.md, workspace documentation, or README files in any IDE. If no configuration is found, the skill discovers available projects via MCP search and prompts you to select one.

Detection fails when the configuration file is missing from the workspace root or `.cursor/rules/` directory, or lacks required values like Project Key, Cloud ID, and URL. Verify the format matches the documented examples.

Yes, create a subtask by setting issueTypeName to "Subtask" and providing the parent field with the parent issue key, such as "KAN-789". The parent issue must already exist in the same project.

Do not use it for Confluence pages; use the confluence-assistant skill instead. It is scoped to Jira issue operations like search, create, update, transition, and comments only.