use-jira-cli_skill

Overview

This skill provides a concise command-line guide for using the Jira CLI to manage issues, sprints, epics, boards, and projects without leaving the terminal. It emphasizes non-interactive usage and gives practical command patterns for listing, creating, viewing, editing, assigning, and transitioning issues. The guidance is designed for reliable automation and scripting workflows.

How this skill works

The skill inspects and documents the jira command-line tool usage patterns and required flags, focusing on non-interactive modes (--plain or --raw) to avoid blocking prompts. It explains core commands for issue, sprint, epic, board, and configuration operations and shows common filters and output formats for human-readable or machine-parsable results. The content highlights required environment setup (JIRA_API_TOKEN) and safe command forms for automation.

When to use it

• You want to list, search, or filter Jira issues from a terminal or script.
• You need to create or edit issues non-interactively as part of automation.
• You must manage sprints or view current sprint data in CI or daily checks.
• You need JSON output for parsing or integrations (--raw).
• You want to move issue status or assign issues without opening the web UI.

Best practices

• Always append --plain or --raw to avoid interactive prompts and hanging processes.
• Use --raw for JSON when programmatic parsing or tooling integration is required.
• Include required fields and --no-input when creating or editing issues to prevent prompts.
• Validate your API token and run jira me or jira serverinfo to confirm connectivity before batch operations.
• Specify project (-p PROJECT_KEY) or issue IDs explicitly to avoid operating in the wrong project.

Example use cases

• Automate a daily standup report: jira issue list -a$(jira me) -s"In Progress" --plain.
• Create a ticket from a CI job: jira issue create -t"Bug" -s"Build failure" -b"Logs attached" --no-input.
• Move and assign when starting work: jira issue assign ISSUE-123 $(jira me) && jira issue move ISSUE-123 "In Progress".
• Export sprint details for analytics: jira sprint list --current --raw > sprint.json.
• Add an issue to an epic in a merge pipeline: jira epic add EPIC-123 ISSUE-456