Problem

The --custom flag on jira issue create does not support cascading select fields. These fields require a nested JSON structure like:

{"value": "Parent Option", "child": {"value": "Child Option"}}

When attempting to pass a cascading select field via --custom, the CLI warns:

Some custom fields are not configured and will be ignored.
Invalid custom fields used in the command: customfield_12345

Even after configuring the field in .config.yml, cascading select is listed as an unsupported datatype (per #346).

Use Case

Many Jira projects have required cascading select fields (e.g., a "Team" field with parent department and child team). Currently, non-interactive issue creation (--no-input) is impossible for these projects because:

1. --custom doesn't support cascading select schema
2. --no-input skips interactive prompts that might otherwise handle it

Expected Behavior

Support cascading select values via --custom with a syntax like:

# Option A: JSON value
jira issue create -tStory -s"Title" --custom 'team-field={"value":"Engineering","child":{"value":"Backend"}}'

# Option B: Arrow/delimiter syntax
jira issue create -tStory -s"Title" --custom 'team-field=Engineering->Backend'

Environment

• jira-cli version: v1.7.0
• Go version: go1.25.6
• OS: macOS (darwin/arm64)

Related

• How can I set custom fields on issue creation? #346 (custom fields discussion — lists cascading select as unsupported)