jira-journey

Execute JIRA ticket validation journeys with Playwright across viewports and capture evidence.

3|3|Updated Jan 18, 2026
One-click install
npx skills add https://github.com/CodySwannGT/lisa --skill jira-journey
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jira-journey
Source: https://github.com/CodySwannGT/lisa/tree/main/plugins/lisa-expo/skills/jira-journey
Command: npx skills add https://github.com/CodySwannGT/lisa --skill jira-journey

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jira-cli, gh, and includes scripts (resource) components.

What problem does it solve?

This Skill automates the tedious process of validating JIRA tickets by executing defined steps across multiple browser viewports, capturing evidence, and reporting results.

Core Features & Use Cases

  • Automated Validation: Executes steps defined in a JIRA ticket's "Validation Journey" section.
  • Cross-Viewport Testing: Runs tests across specified desktop and mobile viewports.
  • Evidence Capture: Takes screenshots at defined markers and generates reports.
  • Use Case: A QA engineer can use this Skill to automatically test a new feature described in a JIRA ticket, ensuring it works correctly on both desktop and mobile devices, and generating a report with screenshots for review.

Quick Start

Execute the validation journey for JIRA ticket PROJ-123.

Frequently Asked Questions about jira-journey

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate JIRA ticket validation with Playwright?

You can automate JIRA ticket validation by executing the steps defined in a JIRA ticket's Validation Journey section. This Skill runs Playwright across multiple browser viewports, captures screenshots at specified markers, and generates evidence reports automatically.

How do I capture validation evidence and post it to JIRA and GitHub PRs?

To capture validation evidence, this Skill takes screenshots at defined markers during the Playwright test execution. It then generates evidence templates in both JIRA wiki markup and GitHub markdown formats, and automatically posts the evidence to JIRA and GitHub PRs.

Can I run Playwright cross-viewport testing for JIRA tickets on both desktop and mobile?

Yes, cross-viewport testing is supported for JIRA ticket validation. The Skill runs the defined Playwright validation journeys across specified desktop and mobile viewports to ensure the feature works correctly on different devices.

Do I need jira-cli and gh to automate ticket validation and evidence reporting?

Yes, you need both jira-cli and gh installed as dependencies. These command-line tools are required to interact with JIRA and GitHub, enabling the Skill to read validation journeys and post the generated evidence reports back to JIRA and GitHub PRs.

What's the best way to generate QA evidence templates from automated browser tests?

The best way to generate QA evidence templates is by automating the validation journey with Playwright. This Skill captures screenshots at specified markers during execution and produces evidence templates in both JIRA wiki markup and GitHub markdown formats for review.

Why should I use automated validation journeys instead of manual QA testing for JIRA tickets?

Automated validation journeys solve the tedious process of manually testing JIRA tickets across multiple viewports. By executing defined Playwright steps and automatically capturing screenshot evidence, it ensures consistent cross-device validation and generates standardized reports for review.