jira-custom-fields

Jira custom fields discovery uses the jira-as CLI to enumerate all fields and identify Agile configurations like Story Points and Sprint across multi-project environments. Running `jira-as fields list` outputs project-specific field availability to reduce admin overhead and misconfigurations.

Agile custom fields configuration for company-managed Jira projects is prepared and applied directly through API interactions using the jira-as CLI. The Skill generates and applies context-aware field configurations to ensure Agile readiness for project scopes.

Team-managed Jira projects have limited API access for custom field configuration. The Skill guides you through UI configuration steps to apply field settings when direct REST API interactions are restricted for team-managed project types.

Auditing Jira custom fields for governance involves maintaining a field registry with naming standards and context-aware configurations. The Skill establishes this registry to support scale and compliance across multi-project environments using jira-as CLI enumeration outputs.

Yes, jira-as CLI supports checking Agile field readiness for a specific project. Running `jira-as fields check-project PROJ` verifies the availability and correct configuration of required Agile fields like Epic Link and Story Points.