fxa-jira-bug-description

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.

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.

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.

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.

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.

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.