jira-workflow_skill

Overview

This skill integrates Jira Cloud project management through the MorphixAI proxy. It lets you search, create, update, transition, and comment on issues, and view projects and boards without handling OAuth tokens directly. The tool converts Markdown to Jira ADF automatically and uses linked Jira accounts for secure API access.

How this skill works

The skill issues commands to the MorphixAI agent (mx_jira) which performs Jira Cloud API v3 calls on your behalf. It handles authentication via MORPHIXAI_API_KEY and an mx_link-linked Jira account, converts Markdown to ADF, and auto-resolves transitions so you rarely need transition IDs. Typical actions include list_projects, search_issues, get_issue, create_issue, update_issue, transition_issue, get_transitions, and add_comment.

When to use it

• Run scoped JQL searches for backlog grooming or daily standups.
• Create new issues with Markdown descriptions and set priority/labels.
• Transition issues through workflow states without finding transition IDs manually.
• Add developer or stakeholder comments that preserve Markdown formatting.
• Inspect project and board lists to plan sprints or releases.

Best practices

• Always include project and other limiting clauses in JQL (e.g., project = PROJ) to avoid broad queries.
• Link your Jira account with mx_link and set MORPHIXAI_API_KEY in the environment before running commands.
• Use Markdown for descriptions and comments; the skill will convert to JIRA ADF automatically.
• When transitioning, prefer target status names; the tool will find matching transitions or list available ones if the target is unreachable.
• Keep updates minimal and use fields map for structured changes (e.g., {"summary": "...", "priority": {"name": "High"}}).

Example use cases

• Daily standup: get_myself to fetch accountId, then search_issues for assigned unfinished work sorted by priority.
• Start work: create_issue, then transition_issue to "In Progress" and add_comment "Starting work".
• Complete work: add_comment with PR link, then transition_issue to "Done".
• Bulk triage: list_projects then search_issues with project-limited JQL to identify stale tickets for closure.