fields

List Jira field metadata for a project and optional issue type.

46|12|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/mulhamna/jira-commands --skill fields-mulhamna
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fields
Source: https://github.com/mulhamna/jira-commands/tree/main/plugin/skills/fields
Command: npx skills add https://github.com/mulhamna/jira-commands --skill fields-mulhamna

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes guesswork when creating or updating Jira issues by helping you discover the correct field set and field constraints for a specific project and issue type.

Core Features & Use Cases

  • Project- and issue-type-specific field discovery: Lists available Jira fields for a chosen project, optionally filtered by issue type.
  • Required-field inspection for safer workflows: Lets you focus on required fields before you start a create/update flow.
  • Backlog/custom-field readiness: Helps teams understand custom field IDs and expected value shapes to avoid payload errors.

Quick Start

Run fields for your project to identify the field IDs you should include in your next Jira create or update request.

Frequently Asked Questions about fields

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find required Jira fields before creating an issue?

To find required Jira fields, you can list project and issue type metadata to identify mandatory fields and custom field IDs. This prevents payload errors by ensuring you include the correct field constraints before executing create or update flows.

What is the best way to get Jira custom field IDs for a backlog project?

The best way to get Jira custom field IDs is by discovering project-specific field metadata. This surfaces exact custom field IDs and expected value shapes, ensuring your backlog issue payloads match the required schema.

Why does my Jira issue creation fail with payload errors?

Jira issue creation fails with payload errors when you submit incorrect or missing required fields. By discovering specific project and issue type field constraints beforehand, you can validate required fields and avoid these payload mismatches.

Can I filter Jira field metadata by specific issue types?

Yes, you can filter Jira field metadata by specific issue types. Listing fields with an optional issue type filter surfaces only the relevant and required fields for that chosen type, streamlining your create or update workflows.

Do I need to know the field schema to update Jira backlog items?

Yes, knowing the field schema is necessary to update Jira backlog items safely. Inspecting field metadata beforehand reveals expected value shapes and required custom fields, preventing schema mismatch errors during your update flow.