| name | jira-administration |
| description | Complete JIRA project and system administration including projects, automation rules, permissions, users, notifications, screens, issue types, and workflows. Use when managing project structure, automating work, configuring team access, or setting up issue tracking.
|
| version | 1.0.0 |
| author | jira-assistant-skills |
| license | MIT |
| allowed-tools | ["Bash","Read","Glob","Grep"] |
JIRA Admin Skill
Comprehensive administration tools for JIRA Cloud covering 8 major subsystems.
Risk Levels
| Operation | Risk | Notes |
|---|
| List/get (any resource) | - | Read-only |
| Search users | - | Read-only |
| Check permissions | - | Read-only |
| Create project | - | Easily reversible (can delete) |
| Create group | - | Easily reversible (can delete) |
| Create permission/notification scheme | - | Can delete |
| Create issue type | - | Can delete |
| Update project settings | ! | Can be undone |
| Update permission scheme | ! | Can be modified |
| Enable/disable automation | ! | Can toggle back |
| Invoke automation rule | ! | Rule executes; effects vary |
| Add user to group/role | ! | Can remove |
| Remove user from group/role | ! | Can re-add |
| Assign scheme to project | ! | Can reassign |
| Archive project | ! | Can restore |
| Add/remove screen fields | ! | Can reverse |
| Delete issue type | !! | Issues lose type |
| Delete group | !! | Members lose group access |
| Delete permission scheme | !! | Projects lose permissions |
| Delete project | !!! | IRREVERSIBLE - all issues lost |
Risk Legend: - Safe, read-only | ! Caution, modifiable | !! Warning, destructive but recoverable | !!! Danger, irreversible
CRITICAL: Project deletion is irreversible. Always use --dry-run when available.
What This Skill Does
8 Major Administration Areas:
| Area | Key Operations |
|---|
| Project Management | Create, configure, archive, restore projects and categories |
| Automation Rules | Discover, manage, invoke automation rules and templates |
| Permission Schemes | Control who can do what across projects |
| Permission Diagnostics | Check permissions, diagnose 403 errors |
| User & Group Management | Find users, create groups, manage membership |
| Notification Schemes | Configure who receives what notifications |
| Screen Management | Control which fields appear in issue workflows |
| Issue Types & Schemes | Define work item types and their availability |
| Workflow Management | Explore and assign issue lifecycle workflows |
Quick Navigation
In a hurry? Use these:
Common Tasks
Choose Your Task
When to Use This Skill
Reach for this skill when you need to:
Setting up projects:
- Create new JIRA projects with appropriate templates
- Configure project settings (lead, default assignee, avatar)
- Archive inactive projects or restore deleted ones
- Organize projects with categories
Configuring access:
- Define who can view, create, or edit issues
- Create and manage permission schemes
- Assign schemes to projects
Diagnosing permission issues:
- Check which permissions you have on a project
- Identify why a 403 Forbidden error occurred
Automating work:
- List, enable, disable, or invoke automation rules
- Create rules from templates
- Manage rule states during bulk operations
Managing users:
- Search for users by name or email
- Create and manage groups
- Add/remove users from groups
Setting up notifications:
- Configure who gets notified about issue changes
- Create targeted notification schemes
- Minimize notification noise
Configuring screens:
- Add or remove fields from screens
- Discover project screen configurations
- Understand the 3-tier screen hierarchy
Organizing issue types:
- Create custom issue types
- Manage issue type schemes
- Assign schemes to projects
Managing workflows:
- View workflows and their transitions
- Assign workflow schemes to projects
- List and filter statuses
Available Commands
IMPORTANT: Always use the jira-as CLI. Never run Python scripts directly.
All commands support --help for full documentation.
Project Management
jira-as admin project list
jira-as admin project get PROJ
jira-as admin project create
jira-as admin project update PROJ
jira-as admin project delete PROJ
jira-as admin project archive PROJ
jira-as admin project restore PROJ
jira-as admin config get PROJ
jira-as admin category list
jira-as admin category create
jira-as admin category assign PROJ
Automation Rules
jira-as admin automation list --project PROJ
jira-as admin automation list --state enabled
jira-as admin automation list --project PROJ --state enabled
jira-as admin automation get RULE_ID
jira-as admin automation search --query "term"
jira-as admin automation enable RULE_ID
jira-as admin automation disable RULE_ID
jira-as admin automation toggle RULE_ID
jira-as admin automation invoke RULE_ID
jira-as admin automation-template list
jira-as admin automation-template get TEMPLATE_ID
Permission Schemes
jira-as admin permission-scheme list
jira-as admin permission-scheme get ID
jira-as admin permission-scheme create
jira-as admin permission-scheme assign
jira-as admin permission list
Permission Diagnostics
jira-as admin permission check --project DEMO
User & Group Management
jira-as admin user search "name"
jira-as admin user search "john" -g
jira-as admin user search "" -p PROJ -a
jira-as admin user search "" --all
jira-as admin user search "" --all --max-results 100
jira-as admin user get ACCOUNT_ID
jira-as admin group list
jira-as admin group members GROUP_NAME
jira-as admin group create GROUP_NAME
jira-as admin group delete GROUP_NAME -y
jira-as admin group delete GROUP_NAME --dry-run
jira-as admin group add-user GROUP_NAME --user EMAIL
jira-as admin group remove-user GROUP_NAME --user EMAIL -y
Notification Schemes
jira-as admin notification-scheme list
jira-as admin notification-scheme get ID
jira-as admin notification-scheme create
jira-as admin notification add
jira-as admin notification remove
Screen Management
jira-as admin screen list
jira-as admin screen get ID
jira-as admin screen tabs ID
jira-as admin screen fields ID
jira-as admin screen add-field SCREEN_ID FIELD_ID
jira-as admin screen remove-field SCREEN_ID FIELD_ID
jira-as admin screen-scheme list
jira-as admin screen-scheme get SCHEME_ID
Issue Types
jira-as admin issue-type list
jira-as admin issue-type get ID
jira-as admin issue-type create
jira-as admin issue-type update ID
jira-as admin issue-type delete ID
Issue Type Schemes
jira-as admin issue-type-scheme list
jira-as admin issue-type-scheme get ID
jira-as admin issue-type-scheme create
jira-as admin issue-type-scheme assign
jira-as admin issue-type-scheme project
Workflow Management
jira-as admin workflow list
jira-as admin workflow get --name "Name"
jira-as admin workflow search --query "term"
jira-as admin workflow for-issue ISSUE_KEY
jira-as admin workflow-scheme list
jira-as admin workflow-scheme get --id ID
jira-as admin workflow-scheme assign
jira-as admin status list
Getting Started
30-Second Start
jira-as admin project list
jira-as admin config get PROJ
jira-as admin user search "john" --include-groups
Next Steps
- For detailed examples: See docs/subsystems/
- For step-by-step workflows: See docs/WORKFLOWS.md
- For command reference: See docs/QUICK-REFERENCE.md
- For best practices: See docs/BEST_PRACTICES.md
- To find the right script: See docs/DECISION-TREE.md
Common Patterns
Preview Before Changing
jira-as admin project delete PROJ --dry-run
jira-as admin group delete GROUP_NAME --dry-run
jira-as admin permission-scheme assign --project PROJ --scheme 10050 --dry-run
JSON Output for Scripting
jira-as admin project list --output json
jira-as admin workflow get --name "Workflow" --output json
Profile Selection
Permission Requirements
| Operation | Required Permission |
|---|
| Project CRUD | Administer Jira (global) |
| Permission Schemes | Administer Jira (global) |
| Automation Rules | Administer Jira or Project Admin |
| Notification Schemes | Administer Jira (global) |
| Screen Management | Administer Jira (global) |
| Issue Types | Administer Jira (global) |
| Workflows (view) | Administer Jira (global) |
| User/Group (write) | Site Administration |
| User/Group (read) | Browse Users and Groups |
Common Errors
| Error | Solution |
|---|
| 403 Forbidden | Verify you have "Administer Jira" permission |
| 404 Not Found | Check project key, scheme ID, or resource spelling |
| 409 Conflict | Resource exists - choose different name/key |
| 400 Bad Request | Validate input format (see script --help) |
Troubleshooting
Diagnose 403 Forbidden Errors
jira-as admin permission check --project DEMO
Verify Permissions
jira-as admin user search "your.name" --include-groups
jira-as admin project list --type software
Check Configuration
jira-as admin config get PROJ --show-schemes
jira-as admin issue-type-scheme project --project-id 10000
Debug Scheme Assignments
jira-as admin permission-scheme get 10000 --show-projects
jira-as admin workflow-scheme get --id 10100 --show-projects
Template Files
JSON templates for common operations are available in assets/templates/:
| Template | Purpose |
|---|
notification_scheme_minimal.json | Minimal notifications |
notification_scheme_basic.json | Common event-recipient mappings |
notification_scheme_comprehensive.json | Full notifications |
Subsystem Guides
Detailed documentation for each administration area:
| Guide | Content |
|---|
| project-management-guide.md | Projects, categories, configuration |
| automation-rules-guide.md | Rules, templates, state management |
| permission-schemes-guide.md | Permissions, grants, assignment |
| user-group-guide.md | Users, groups, membership |
| notification-schemes-guide.md | Events, recipients, schemes |
| screen-management-guide.md | Screens, tabs, fields |
| issue-types-guide.md | Issue type CRUD |
| issue-type-schemes-guide.md | Scheme management |
| workflow-management-guide.md | Workflows, statuses, schemes |
Related Skills
This skill works well in combination with:
| Skill | Use Case |
|---|
| jira-issue | Core issue CRUD operations (uses projects created here) |
| jira-lifecycle | Workflow transitions (uses workflows configured here) |
| jira-fields | Custom field discovery (integrates with screens) |
| jira-agile | Sprint and board management (uses projects created here) |
| jira-jsm | Service desk configuration (requires JSM projects) |
| jira-bulk | Bulk operations (uses permission schemes) |
| jira-search | JQL queries (uses issue types configured here) |
| jira-ops | Cache management (optimizes admin operations) |
Best Practices
For comprehensive guidance on JIRA administration, see docs/BEST_PRACTICES.md, which covers:
- Project naming conventions and lifecycle management
- Permission scheme design patterns
- Automation rule design principles
- Notification scheme optimization
- Screen management hierarchy
- Issue type and scheme strategies
- Workflow discovery and assignment
- Security considerations
- Performance optimization
- Common pitfalls and solutions
Documentation Structure
jira-admin/
├── SKILL.md # This file - skill overview (discovery)
├── docs/
│ ├── BEST_PRACTICES.md # Comprehensive best practices
│ ├── DECISION-TREE.md # Find the right command
│ ├── WORKFLOWS.md # Step-by-step workflows
│ ├── QUICK-REFERENCE.md # Command syntax reference
│ ├── VOODOO_CONSTANTS.md # Field IDs, event IDs, constants
│ └── subsystems/ # Detailed per-area guides
│ ├── project-management-guide.md
│ ├── automation-rules-guide.md
│ ├── permission-schemes-guide.md
│ ├── user-group-guide.md
│ ├── notification-schemes-guide.md
│ ├── screen-management-guide.md
│ ├── issue-types-guide.md
│ ├── issue-type-schemes-guide.md
│ └── workflow-management-guide.md
└── assets/templates/ # JSON templates