ticket-fields

Included with Lifetime

$97 forever

Discover available Jira fields for a project and issue type. Use when the user needs to find field names, see what fields are available, or discover custom field values before creating or updating tickets.

General

What this skill does


# Discover Jira Fields

Discover what fields are available when creating or updating Jira tickets.

## When to Use

- User needs to find correct field names
- User encounters "field not found" errors
- User wants to see allowed values for select fields
- User is preparing to create/update tickets with custom fields

## How to Execute

Run:

```bash
aide jira fields PROJECT [options]
```

### Options

| Flag            | Short | Description                                         |
| --------------- | ----- | --------------------------------------------------- |
| `--type`        | `-t`  | Issue type (e.g., Task, Bug). If omitted, shows all |
| `--filter`      | `-f`  | Filter: all, required, optional, custom, system     |
| `--show-values` | `-v`  | Display allowed values for select fields            |
| `--max-values`  |       | Maximum values to display per field (default: 10)   |
| `--format`      |       | Output format: text, json, markdown                 |

## Common Patterns

```bash
# List all fields for a project
aide jira fields PROJ

# List fields for a specific issue type
aide jira fields PROJ -t Bug

# Show only required fields
aide jira fields PROJ -t Task --filter required

# Show custom fields with their allowed values
aide jira fields PROJ -t Bug --filter custom --show-values

# Get full field metadata as JSON
aide jira fields PROJ -t Task --format json --show-values
```

## Integration with Create/Update

Once you discover field names, use them directly with **ticket-create** or **ticket-update**:

```bash
# 1. Discover available fields
aide jira fields PROJ -t Bug --filter custom --show-values
# Output shows: Severity (customfield_10269) - select
#   Values: Critical, High, Medium, Low

# 2. Use the field name (auto-resolved to internal ID)
aide jira create -p PROJ -t Bug -s "My bug" --field "Severity=Critical"
aide jira update PROJ-123 --field "Severity=High"
```

The `--field` flag automatically:

- Resolves field names to internal IDs
- Formats values based on field type
- Validates values and shows allowed options on error

## Output Includes

1. Field name (human-readable)
2. Field ID (internal)
3. Field type (text, select, array, etc.)
4. Whether the field is required
5. Allowed values (with `--show-values`)

## Use Cases

| Goal                        | Command                                          |
| --------------------------- | ------------------------------------------------ |
| Find required fields        | `aide jira fields PROJ -t Bug --filter required` |
| See custom fields           | `aide jira fields PROJ --filter custom`          |
| Get allowed values          | `aide jira fields PROJ -t Bug --show-values`     |
| Get metadata for automation | `aide jira fields PROJ --format json`            |

## Best Practices

- Always check fields before creating tickets with custom fields
- Use `--show-values` to see valid options for select fields
- Use `--filter required` to see mandatory fields
- Use `--format json` for programmatic access

## Next Steps

After discovering fields:

- Use **ticket-create** skill to create tickets with correct fields
- Use **ticket-update** skill to update custom fields

Files: 1

Size: 3.4 KB

Complexity: 12/100

Category: General

Source: https://github.com/rlcurrall/aide/tree/main/skills/ticket-fields

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).

Generalscripts

relationship-science-coach

Included

Use this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.

Generalscripts

building-sf-integrations

Included

Salesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).

Generalscripts

venue-templates

Included

Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.

Generalscripts

let-fate-decide

Included

Draws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.

Generalscripts

net-ops

Included

Cross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.

Generalscripts