Bug Tracking System

Features

Industries

Reference

More

Start now
  1. Bug Tracking System
  2. Your Bug Tracking Assistant
Reference

Put an AI agent to work in Bug Tracking System

Start with the ERP.AI skill reference:

Set it up

  1. Teach your agent ERP.AI

    Load the ERP.AI skill and paste the output into your agent. It explains how to read and update records in your workspace.

    curl -fsSL https://www.erp.ai/skill.md

  2. Give it a role

    Assign the agent its own user and one of the 5 roles. It gets exactly the access that role has, and no more.

  3. Check what it can reach

    Confirm which records, actions and connections the agent can use in your workspace before you point it at real data.

  4. Review its work and usage

    Check the drafts and changes it proposes, and watch its usage receipts as you give it more to do. Agent work uses prepaid credits.

What the agent can do

  • Developer: Summarize the reported behavior and identify the corrective task, due date and evidence needed for the QA handoff.
  • QA Engineer: Prepare a retest checklist from the report notes and show defects ready for independent verification.
  • Project Manager: Review blocked tasks and pending milestones before the delivery discussion.
  • Delivery Lead: Compare assigned work with team capacity context and highlight project risks requiring an owner response.

What stays with a person

  • The assistant cannot supply a successful test result that nobody observed or replace the QA Engineer's independent verification decision.
  • It must respect the signed-in person's access and the current source records.
  • A task being Done is insufficient evidence that the defect was verified, and a failed receipt is not a successful operation.
  • AI requests and connected activity use the metering described in [pricing](/bug-tracking-system/pricing).

The assistant cannot supply a successful test result that nobody observed or replace the QA Engineer's independent verification decision. It must respect the signed-in person's access and the current source records. A task being Done is insufficient evidence that the defect was verified, and a failed receipt is not a successful operation.

AI requests and connected activity use the metering described in [pricing](/bug-tracking-system/pricing). Confirm the intended scope before asking the assistant to change delivery records.

Set up Bug Tracking System your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

Start now Download Proto

How to get started