daf-jira-fields

JIRA Field Intelligence for DevAIFlow

Understanding JIRA field mappings, validation rules, and defaults for creating/updating JIRA issues.

Quick Discovery

# Discover YOUR JIRA's custom fields
daf config show --fields

# Refresh from JIRA API
daf config refresh-jira-fields

# View merged config
daf config show

System vs Custom Fields (CRITICAL)

System Fields

Standard JIRA fields with dedicated CLI options:

Fields: components, labels, assignee, reporter, priority, security-level, fixVersions, affectedVersions

Usage:

# ✅ CORRECT
daf jira create bug --components backend --labels urgent --assignee jdoe

# ❌ WRONG - Will error
daf jira create bug --field components=backend  # Error: Use --components option

Array syntax: Comma-separated values

--components backend,frontend,api
--labels urgent,production

Custom Fields

Organization-specific fields with IDs like customfield_12345. Use --field with mapped names.

Discovery:

daf config show --fields

Usage:

# Use YOUR organization's field names (not generic examples)
daf jira create story \
  --summary "Feature" \
  --parent PROJ-1234 \
  --field <your_field_name>=<value>

Never use customfield IDs directly:

# ❌ WRONG
--field customfield_12345=value

# ✅ CORRECT - Use mapped name
--field team_assignment=value

Field Mapping Structure

Location: $DEVAIFLOW_HOME/backends/jira.json

Structure:

{
  "field_mappings": {
    "<field_name>": {
      "id": "customfield_XXXXX",
      "name": "Display Name",
      "type": "option|string|number|array|user|version",
      "required_for": ["Story", "Task"],
      "available_for": ["Story", "Task", "Epic"],
      "allowed_values": ["Value1", "Value2"]
    }
  }
}

Attributes:

• id - JIRA customfield ID
• type - Field type (string, number, option, array, user, version)
• required_for - Issue types where field is required
• available_for - Issue types where field can be used
• allowed_values - Valid values (for select fields)