| name | jira-field-mapping |
| description | Jira field extraction and validation rules for QA agents. Use when fetching Jira story details, extracting acceptance criteria using customfield_14400, mapping custom metadata fields, validating Story IDs, or reading Jira data for test case generation or coverage analysis. |
| user-invocable | false |
Jira Field Mapping
Standard Fields
| Jira Field | Purpose | Usage in Test Cases |
|---|
key | Story ID (e.g., PS-12345) | Validate against user input; appears in every test case |
summary | One-line story title | Rewrite into clean test case section title (not copied) |
description | Business and functional context | Extract: feature area, toggle name, user roles, preconditions |
Custom Fields
| Field Name | Custom Field ID | Usage |
|---|
| Acceptance Criteria | customfield_14400 | Primary source — each active AC maps to ≥1 test case |
| Subvalue Stream | customfield_22201 | Header classification/tagging only |
| Value Stream | customfield_22200 | Header classification/tagging only |
| Portfolio Team | customfield_15604 | Organizational metadata — optional, do not influence logic |
Extraction Rules
Story ID Validation (Mandatory First Step)
- Fetch story using
@jira tool — format: Get issue <STORY-ID> or Search for story <STORY-ID>
- Verify the returned
key field exactly matches the Story ID provided by the user
- If mismatch: stop processing and respond with the governance error message
- Never use GitHub search, filesystem, or other tools to look up Jira story content
Acceptance Criteria (customfield_14400)
- Primary driver for all test case generation
- Ignore strikethrough entries — they are deprecated/invalid
- Never mix multiple ACs into one test scenario
- Each AC must produce ≥1 test case
- Every test case must reference its parent AC ID in the header
Description Field
- Never copy Jira description text directly into test cases
- Always rewrite in clean, professional test language
- Extract from description:
- Feature toggle name(s) and their default state (ON/OFF)
- Required user roles and access rights
- System entry points (navigation paths)
- Any business rules or conditions mentioned
Metadata Fields (Value Stream, Subvalue Stream, Portfolio Team)
- Use only for populating the test case file header
- These fields must NOT influence functional test logic, scenario derivation, or coverage decisions
Feature Toggle Detection
Scan the description field for:
- Feature flag/toggle names (LaunchDarkly flags, feature flags, config flags)
- Default state (ON/OFF by default)
- Access conditions tied to the toggle
Mandatory: Every story MUST have at least one test case with the feature toggle set to OFF (<STORY-ID>-TOGGLE-TC010).
Single Jira Call Pattern
Retrieve all required fields in a single Jira tool call:
Get issue PS-12345
Expected fields to extract in one pass:
key, summary, descriptioncustomfield_14400 (Acceptance Criteria)customfield_22200 (Value Stream)customfield_22201 (Subvalue Stream)customfield_15604 (Portfolio Team)
