fxa-jira-bug-description

Name: fxa-jira-bug-description
Availability: InStock
Author: Mozilla

Generate structured Jira bug reports for FXA issues from logs or Sentry events.

683|238|Updated Jun 3, 2015

Search Tags:#jira #triage #root-cause #issue-tracking #reproduction-steps #bug-report #fxa

Ready to run

npx skills add https://github.com/mozilla/fxa --skill fxa-jira-bug-description

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: fxa-jira-bug-description
Source: https://github.com/mozilla/fxa/tree/main/.claude/skills/fxa-jira-bug-description
Command: npx skills add https://github.com/mozilla/fxa --skill fxa-jira-bug-description

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Drafts a Jira bug report for FXA issues by collecting reproduction steps, observed vs expected behavior, and affected surface, then outputs a structured report ready for filing or handoff to investigation.

Core Features & Use Cases

Automates gathering reproduction steps, expected vs actual behaviour, and affected surface
Outputs a structured Jira bug report ready to file or hand off to a teammate
Guides the user to provide missing information

Quick Start

Provide a Sentry link or error details and let the tool generate a Jira bug report.

Frequently Asked Questions about fxa-jira-bug-description

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

FAQPage Schema

How do I create a Jira bug report from a Sentry event for FXA issues?▼

To create a Jira bug report from a Sentry event, provide the error details or Sentry link to the tool. It extracts reproduction steps, expected versus actual behavior, and the affected surface, then outputs a structured report ready to file.

What information is needed to draft a Jira bug report for Firefox Accounts?▼

Drafting a Jira bug report for Firefox Accounts requires reproduction steps, expected and actual behavior, and the affected surface. The tool guides you to provide any missing required fields, including browser, OS environment, and account state when relevant.

Can I generate Jira bug reports directly from user reports and logs?▼

Yes, you can generate Jira bug reports directly from user reports and logs. The tool processes issue descriptions from these sources and structures them into a concise one-sentence summary alongside the required steps and behaviors for filing.

Does the FXA bug report generator work without entering reproduction steps manually?▼

The FXA bug report generator requires reproduction steps to output a valid report. If you provide incomplete information, it prompts you to supply the missing steps, expected versus actual behavior, and the affected surface before generating the structured filing.

What is the best way to structure a Jira bug report for FXA triage?▼

The best way to structure a Jira bug report for FXA triage is to include a concise one-sentence description, reproduction steps, expected and actual behavior, and the affected surface, which this tool generates automatically from your input logs or events.

Why does my FXA Jira bug report need the affected surface and account state?▼

Your FXA Jira bug report needs the affected surface and account state to provide complete context for investigation. Including browser, OS environment, and account state ensures the structured report is ready for accurate root-cause analysis and handoff.