skills.rest
carlos-algms
carlos-algmsCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

jira-atlassian-cli

Load Jira team and sprint context before creating or editing work items.

2|Updated Jun 1, 2017
Search Tags:#mcp#jira#atlassian#work items#adf#acli#sprint mapping
One-click install
npx skills add https://github.com/carlos-algms/dotfiles --skill jira-atlassian-cli
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: jira-atlassian-cli
Source: https://github.com/carlos-algms/dotfiles/tree/main/AI-configs/skills/jira-atlassian-cli
Command: npx skills add https://github.com/carlos-algms/dotfiles --skill jira-atlassian-cli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents missing required Jira fields by establishing team, project, sprint, and custom-field mappings before any Jira tool interaction or MCP call that creates or updates issues.

Core Features & Use Cases

  • Team and sprint context loading: Reads the entire per-session team context file and resolves the correct team values and placeholders.
  • Correct Jira field population: Enforces required additional_fields mappings and numeric sprint field formatting to avoid invalid tickets.
  • MCP-first workflow with acli fallback: Prefer mcp__atlassian__* for create/edit/search/transition and use acli when MCP is unavailable or insufficient.

Quick Start

Use the jira-atlassian-cli skill when prompted to create, read, edit, search, or transition a Jira ticket described by a Jira URL or key like ABC-123, and then proceed with the requested operation.

Frequently Asked Questions about jira-atlassian-cli

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why does creating Jira work items fail with missing required fields?▼

Creating Jira work items fails when team and sprint context is not resolved before the API call. Loading a dedicated YAML file enforces required field mappings and placeholder substitution to prevent invalid tickets.

How do I create Jira tickets using Atlassian MCP without field validation errors?▼

To create Jira tickets via Atlassian MCP without errors, enforce full team context loading and apply correct `additional_fields` mappings. This ensures numeric sprint fields and custom fields are formatted properly before the tool call.

What is the correct contentFormat for Jira ADF and markdown when editing work items?▼

The correct contentFormat requires strict validation of Jira Atlassian Document Format (ADF) nodes and field types, applying placeholder substitution rules to ensure ADF or markdown content is structured correctly before submission.

Can I use acli as a fallback when the Atlassian MCP is unavailable?▼

Yes, you can use acli as a fallback for create, read, edit, search, and transition workflows when Atlassian MCP is unavailable or insufficient. The MCP-first approach is preferred but acli ensures continuous Jira operations.

How do I map sprints and link issues when transitioning Jira tickets?▼

To map sprints and link issues during Jira ticket transitions, resolve sprint context first to apply correct numeric sprint field formatting. This enforces valid ticket updates and proper issue linking across the team workflow.

Related Skills

Explore More Product & Management Skills→
alexismanuelalexismanuel

jira-ticket-creator

Create and manage Jira tickets for the RD project via CLI.

Community
Advanced
marcuskroghmarcuskrogh

jira

Manage Jira issue transitions and link pull requests via REST API.

Community
Advanced
jyasuujyasuu

acli

Automate Atlassian CLI installation and authentication for Jira and Confluence workflows.

Community
Basic
ChanghwanKChanghwanK

handoff:pause

Save current work context into structured JSON for session handoffs.

Community
Advanced