dmmulroy/.dotfiles

Overview

This skill provides a CLI for creating, updating, transitioning, and managing Jira tickets using Cloudflare Access authentication. It exposes common Jira operations as simple shell commands and returns JSON output suitable for scripting and pipelines. Use it to automate workflows, query issues with JQL, and integrate Jira actions into CI/CD or local tooling.

How this skill works

Commands are invoked via a shell script that authenticates through cloudflared and the Cloudflare Access flow; the first run opens a browser for login and tokens are valid for 24 hours. The tool maps common Jira REST operations (create, get, update, comment, transition, assign, search, delete) to short commands and prints JSON for easy parsing with tools like jq. Transitions can be listed or executed by name, and create supports types, priorities, labels, epics, and parent links for sub-tasks.

When to use it

• Creating new Jira issues from scripts or local workflows
• Automating status transitions and ticket lifecycle steps
• Adding comments, assigning, or updating tickets programmatically
• Running JQL searches and extracting issue data for reports
• Integrating Jira actions into CI/CD, deployment, or developer tooling

Best practices

• Use the search command to look up usernames or existing issues before assigning or linking.
• Parse JSON output with jq in scripts to handle fields like status, assignee, and key reliably.
• Prefer explicit transitions by name; list available transitions first to avoid state errors.
• Provide required flags (project -p and summary -s) when creating issues to prevent failures.
• Keep cloudflared session active (status command) and re-authenticate in the browser when prompted.

Example use cases

• Create a task and immediately transition it to In Progress from a CI job.
• Attach a deployment comment to a ticket: scripts/jira-tool.sh comment PROJ-123 "Deployed to staging".
• Batch update: search with JQL then loop over results to assign or set priority.
• Create a sub-task under an existing issue for breaking down work items.
• Close stale issues by searching recently inactive tickets and running the close command.