jira-admin_skill

Overview

This skill provides complete JIRA Cloud administration across projects, automation, permissions, users, notifications, screens, issue types, and workflows. It centralizes common admin operations into safe, reversible commands and highlights destructive actions so you can avoid irreversible mistakes. Use it to set up projects, automate work, and diagnose permission issues quickly.

How this skill works

The skill exposes a CLI-driven set of commands that list, create, update, assign, and delete JIRA resources across eight administration areas. Commands support dry-run previews, JSON output for scripting, and filters for targeted actions. Risk levels are documented for each operation so you know which actions are safe, cautionary, or potentially irreversible.

When to use it

• Creating or configuring new projects and project categories
• Defining or assigning permission and notification schemes to projects
• Managing users and groups: search, create, add/remove membership
• Listing, enabling, disabling, or invoking automation rules and templates
• Customizing screens, fields, issue types, and issue type schemes
• Diagnosing 403/permission issues and debugging scheme assignments

Best practices

• Always run --dry-run for destructive commands (delete, assign, archive) before executing
• Use JSON output for automation and to capture results in CI pipelines
• Prefer reversible changes (archive, toggle) before permanent deletes; note project deletion is irreversible
• Limit scope when testing automation rules by using project filters or manual invocation
• Document scheme and workflow assignments to avoid surprise permission regressions

Example use cases

• Onboard a new team by creating a project, assigning a permission scheme, and adding users to groups
• Reduce notification noise by creating a targeted notification scheme and assigning it to a project
• Automate repetitive updates: list automation templates, create a rule, enable it, and test with manual invoke
• Diagnose a developer's 403: run permission check on the project and inspect permission schemes and group membership
• Reorganize screens: list project screens, add/remove fields on the screen used by the workflow