> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cassidyai.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Bug Report Structurer

> Streamlines bug reporting for clearer, faster resolutions, enhancing team collaboration and reducing engineering effort.

<Frame>
  <img src="https://mintcdn.com/cassidy/sYy-vNuqpU0xqerK/images/use-cases/bug-report-structurer-img-0.png?fit=max&auto=format&n=sYy-vNuqpU0xqerK&q=85&s=73c6ce3fe218b625797a6a7d171f5c74" alt="Bug Report Structurer" width="1920" height="1080" data-path="images/use-cases/bug-report-structurer-img-0.png" />
</Frame>

## What does this mean?

Improves clarity and consistency of reports, reducing the time engineers spend deciphering issues and accelerating resolution, while enhancing collaboration between product managers and development teams.

Converts raw bug reports into standardized, detailed formats suitable for Jira, preserving context, involved systems, and necessary technical details for engineers.

## Workflow steps

<Steps>
  <Step title="Submit raw bug report">
    The Workflow activates via a Manual trigger when a team member submits a raw bug report—whether it's a quick Slack message, an email from a customer, or notes jotted down during testing.
  </Step>

  <Step title="Parse and extract key details">
    Cassidy analyzes the unstructured report to identify critical information: the issue description, steps to reproduce, affected systems, environment details, and any error messages or screenshots referenced.
  </Step>

  <Step title="Structure into Jira-ready format">
    Using the Generate Text with Cassidy Agent action, the Workflow transforms the extracted details into a standardized bug report template—complete with severity level, affected components, reproduction steps, and technical context engineers need to diagnose the issue.
  </Step>

  <Step title="Route for review">
    The structured report is sent to the product manager or reporter via Request Input from Team for a quick review, ensuring accuracy before it reaches engineering.
  </Step>

  <Step title="Create Jira ticket">
    Once approved, the Workflow sends the formatted bug report directly to Jira via API request, creating a ticket with all fields populated and proper labels applied—ready for engineering to pick up without back-and-forth clarification.
  </Step>
</Steps>

## Related

<CardGroup cols={2}>
  <Card title="Build and configure an Agent" icon="robot" href="/agents/build-and-configure">
    Create a custom Agent with tailored instructions and Knowledge Base access.
  </Card>

  <Card title="Set up your Knowledge Base" icon="book" href="/knowledge-base/setup">
    Add your company documents so Agents can reference them.
  </Card>
</CardGroup>
