Is there a way to test changes before applying them to JIRA?

Yes, the `configure-agile` command supports a `--dry-run` flag which allows you to preview the configuration changes without actually applying them.

Can I use this for Team-managed (next-gen) projects?

Yes, but with limitations. Team-managed projects have restricted API support for field configuration; most deep modifications must still be done through the JIRA UI.

Does this skill require JIRA administrator permissions?

Listing and checking fields only requires standard 'Browse Projects' permissions, but creating new fields or modifying project configurations requires JIRA Administrator access.

How do I find the specific ID for my Story Points field?

You can run the command `jira-as fields list --agile` to display all Agile-related fields and their specific custom field IDs for your instance.

JIRA Custom Field Manager

Name: JIRA Custom Field Manager
Author: grandcamel

bygrandcamel

•

Collaboration Tools

Manages and configures JIRA custom fields, Agile workflows, and project-specific field mappings directly within Claude.

About

This skill empowers Claude to audit, create, and configure JIRA custom fields for both company-managed and team-managed projects. It simplifies complex Agile setups by automating the identification and assignment of Story Points, Epic Links, and Sprint fields, while providing diagnostic tools to troubleshoot field visibility issues and project-type compatibility. By using the jira-as CLI, users can safely explore instance-wide field configurations and automate administrative tasks that typically require navigating complex JIRA UI menus.

Key Features

Project-level field availability and issue type auditing
Automated Agile field configuration for company-managed projects
Administrative custom field creation and project type detection
Instance-wide custom field discovery with name and type filtering
Agile-specific field identification (Story Points, Epic Links, Sprints)
3 GitHub stars

Use Cases

Troubleshooting 'Field not found' or visibility errors during issue creation
Setting up new JIRA projects with standardized Agile field configurations
Auditing and cleaning up unused custom fields across a JIRA instance

About

Key Features

Project-level field availability and issue type auditing
Automated Agile field configuration for company-managed projects
Administrative custom field creation and project type detection
Instance-wide custom field discovery with name and type filtering
Agile-specific field identification (Story Points, Epic Links, Sprints)
3 GitHub stars

Use Cases

Troubleshooting 'Field not found' or visibility errors during issue creation
Setting up new JIRA projects with standardized Agile field configurations
Auditing and cleaning up unused custom fields across a JIRA instance