playbooks

home / skills / hoangnguyen0403 / agent-skills-standard / jira-integration

jira-integration skill

/skills/quality-engineering/jira-integration

This skill helps you manage Jira and Zephyr integration by retrieving issue details and linking test cases for traceability.

npx playbooks add skill hoangnguyen0403/agent-skills-standard --skill jira-integration

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
1.9 KB
---
name: Jira Integration
description: Standards for retrieving Jira issue details and linking Zephyr test cases back to Jira.
metadata:
  labels: [jira, zephyr, integration, traceability]
  triggers:
    files: ['**/jira_*.xml', '**/test_case.json']
    keywords: [jira issue, link zephyr, jira details, jira mcp]
---

# Jira Integration Standards

## **Priority: P1 (HIGH)**

## 1. Retrieving Issue Details

- **Fetch Core Info**: Retrieve Summary, Description, Acceptance Criteria, and Labels.
- **Sibling Analysis**: Identify other Jira issues with the same **Component** or **Labels** to find potentially impacted Zephyr TCs.
- **Identify Links**: Check for existing links to Zephyr test cases to avoid duplication.
- **Actor Mapping**: Extract reporter and assignee for context.

## 2. Linking Zephyr Test Cases

- **Traceability**: After creating a Zephyr Test Case, link it back to the corresponding Jira Issue.
- **Format**: Use the Zephyr Scale key (e.g., `PROJ-T123`) in the Jira link or comment.
- **Labels**: Add `has-zephyr-tests` label to the Jira issue once test cases are linked.

## 3. Jira-Zephyr Workflow

1. **Fetch**: Get Jira User Story details via [Jira MCP](../../common/security-standards/SKILL.md).
2. **Generate**: Create Zephyr Test Case using [Zephyr Generation Skill](../zephyr-test-generation/SKILL.md).
3. **Link**: Use Zephyr MCP tool `create_test_case_issue_link` to bridge the two.
4. **Notify**: Add a comment to Jira: `Linked Zephyr Test Case: {test_case_key}`.

## 4. Best Practices

- **Concise Summaries**: Keep Jira comments professional and brief.
- **Traceability Matrix**: Ensure every AC in Jira has at least one linked Zephyr Test Case.
- **Cleanup**: Remove unused labels or outdated links during refactors.

## 5. Anti-Patterns

- **No Ghosting**: Create tests then link to Jira (Traceability).
- **No Spam**: Post single comment per link.
- **No Missing Labels**: Update Jira labels after linking.

Overview

This skill defines standards for retrieving Jira issue details and linking Zephyr test cases back to Jira to ensure traceability and reduce duplication. It prescribes the fields to fetch, how to analyze related issues, and the exact linking and labeling conventions to maintain clean workflows. The goal is consistent, auditable links between requirements and tests.

How this skill works

The agent fetches core Jira issue data (summary, description, acceptance criteria, labels, reporter, assignee) and scans sibling issues by component or labels to find related test impact. It generates Zephyr Test Cases via the Zephyr creation tool, then creates a link from the test case back to the Jira issue using a standardized link call and posts a concise Jira comment. Finally, it updates Jira labels to reflect test coverage and avoids duplicate links.

When to use it

  • When creating Zephyr test cases for a Jira user story or bug.
  • When assessing test coverage for a Jira component or label scope.
  • Before refactoring or cleanup to identify stale test links and labels.
  • When automating end-to-end traceability between requirements and tests.
  • When preventing duplicate Zephyr test cases for related Jira issues.

Best practices

  • Always fetch Summary, Description, Acceptance Criteria, Labels, Reporter, and Assignee for context.
  • Scan sibling issues by Component and shared Labels to detect impacted cases before creating new tests.
  • Link Zephyr test cases using the Zephyr key format (e.g., PROJ-T123) and add a single concise Jira comment per link.
  • Add or maintain a has-zephyr-tests label on the Jira issue after linking to indicate coverage.
  • Ensure at least one Zephyr test case maps to each acceptance criterion for clear traceability.
  • During cleanup, remove outdated labels and stale test links to keep Jira accurate.

Example use cases

  • Automated generation of Zephyr test cases when a new user story is created, with immediate linkage and labeling in Jira.
  • Periodic audit job that finds Jira issues without has-zephyr-tests label and generates missing test cases.
  • Pre-release verification: scan related components for recent Jira changes and ensure Zephyr coverage is linked.
  • Refactor cleanup: detect and remove duplicate Zephyr links and obsolete has-zephyr-tests labels.
  • Developer workflow: when a tester creates a new test, automatically link it back and notify the assignee.

FAQ

What fields must the agent always fetch from Jira?

Fetch Summary, Description, Acceptance Criteria, Labels, Reporter, and Assignee for full context.

How should the agent format links to Zephyr test cases in Jira?

Include the Zephyr Scale key (e.g., PROJ-T123) in the link or Jira comment and use the dedicated link call to create a reversible association.

How many comments should the agent post per link?

Post a single concise comment per linked test case to avoid spamming the Jira issue.