---
name: tracker/jira-official:field-read
description: Read available JIRA fields
version: "0.5.0"
---

# Field Read

> **Backend:** jira-official (atlassian@claude-plugins-official)

> **Note:** Requires `atlassian@claude-plugins-official` plugin. Install: `/plugin install atlassian@claude-plugins-official`

Retrieves the list of available fields for a JIRA issue type within a project, including custom fields.

## Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| project_key | string | Yes | JIRA project key (e.g., `<PROJECT_KEY>`) |
| issue_type_id | string | Yes | Issue type ID to retrieve field metadata for |

## Implementation

Uses MCP JIRA tool: `mcp__atlassian__getJiraIssueTypeMetaWithFields`

```
mcp__atlassian__getJiraIssueTypeMetaWithFields({
  project_key: "<project_key>",
  issue_type_id: "<issue_type_id>"
})
```

## Output

| Field | Type | Description |
|-------|------|-------------|
| fields | array | List of field descriptor objects |
| fields[].id | string | Field ID used in API calls (e.g., `customfield_10014`) |
| fields[].name | string | Human-readable field name |
| fields[].required | boolean | Whether the field is required for issue creation |
| fields[].schema | object | Field type schema |
| fields[].allowedValues | array | Permitted values for constrained fields |

## Errors

| Code | Cause | Recovery |
|------|-------|----------|
| 404 | Project key or issue type ID not found | Verify both values against the JIRA project configuration |
| 403 | Insufficient permissions to list fields | Confirm the JIRA user has browse project permissions |
| MCP | Plugin unavailable | Verify the `atlassian@claude-plugins-official` plugin is installed and connected |

## Used By

- design-feature (discovering custom field IDs before creating or updating issues)
