Bug Tracking System records defects against projects and follows them from Open through triage, corrective work, independent verification and closure. A defect carries its summary, severity, reporter notes and owner.
Projects in one list
| Project code | Project name | Organization | Owner | Start date | End date | |
|---|---|---|---|---|---|---|
| PROJ-PORTAL-26 | Customer portal reliability release | Cedar Vale Services | Priya Menon | 12 Oct | 19 Oct | |
| PROJ-MOBILE-26 | Warehouse mobile rollout | Harborline Field Operations | Theo Bennett | 12 Oct | 21 Oct | |
| PROJ-BILLING-26 | Billing migration verification | Cedar Vale Services | Camila Souza | 20 Oct | 27 Oct | |
| PROJ-DISPATCH-26 | Field service scheduling upgrade | Willow Creek Utilities | Mateo Ruiz | 02 Nov | 10 Nov | |
| PROJ-PARTNER-26 | Partner API hardening | Mossbridge Retail Group | Mateo Ruiz | 12 Oct | 15 Oct |
QA Engineer independently approves verification after retesting the reported behavior and inspecting the correction evidence.
Every feature works on the same records. Pick one to see the screen your team works in.
Record the reported behavior, assess severity and put each defect into an owned project queue.
Verified waits for the QA engineer
| Issue key | Defect summary | Severity | Project | Owner | Reported by | |
|---|---|---|---|---|---|---|
| BUG-1427 | Duplicate invoice email after retry | Critical | Returns workflow redesign | Camila Souza | Jonas Weber | |
| BUG-1428 | Scanner freezes after reconnect | High | Reporting dashboard refresh | Amara Diallo | Elias Hart | |
| BUG-1429 | Webhook replay creates two tickets | Medium | Partner API hardening | Nina Okafor | Yuki Tanaka | |
| BUG-1430 | CSV export misses last day | Low | Partner API hardening | Elias Hart | Mateo Ruiz | |
| BUG-1431 | Viewer can open admin menu | Critical | Access control remediation | Leila Farouk | Amara Diallo |
Organize corrective tasks by work package, assign the next action and keep blocked work visible.
Tasks
| Task key | Title | Priority | Assignee | Work package | Project | |
|---|---|---|---|---|---|---|
| TASK-2081 | Fix duplicate invoice notification | Low | Leila Farouk | Dispatch calendar updates | Returns workflow redesign | |
| TASK-2082 | Reproduce mobile scan timeout | Medium | Mateo Ruiz | Partner webhook reliability | Reporting dashboard refresh | |
| TASK-2083 | Add retry for partner webhook | High | Leila Farouk | Executive report filters | Warehouse mobile rollout | |
| TASK-2084 | Verify export date filters | Critical | Jonas Weber | Executive report filters | Customer portal reliability release | |
| TASK-2085 | Repair role based menu access | Low | Theo Bennett | Portal authentication fixes | Reporting dashboard refresh |
Have a QA Engineer independently check the reported behavior and retain the evidence behind acceptance.
Tasks
| Task key | Title | Priority | Status | Start date | Due date | |
|---|---|---|---|---|---|---|
| TASK-2081 | Fix duplicate invoice notification | Low | Backlog | 20 Oct | 25 Oct | |
| TASK-2082 | Reproduce mobile scan timeout | Medium | In progress | 25 Oct | 03 Nov | |
| TASK-2083 | Add retry for partner webhook | High | In review | 25 Oct | 30 Oct | |
| TASK-2084 | Verify export date filters | Critical | Blocked | 15 Oct | 20 Oct | |
| TASK-2085 | Repair role based menu access | Low | Done | 17 Oct | 21 Oct |
Place the defect queue within the project's scope, work-package dates and delivery checkpoints.
Review decisions
| Decision number | Subject type | Subject reference | Decision | Decided at | Notes | |
|---|---|---|---|---|---|---|
| RD-58449 | Project | BUG-1427 | Approved | 30 Oct | Retest with the October invoice batch | |
| RD-37626 | Work Package | TASK-2082 | Approved | 28 Oct | Awaiting mobile pilot evidence | |
| RD-87064 | Task | PROJ-BILLING-26 | Approved | 19 Oct | QA signoff needed before release | |
| RD-41716 | Milestone | WP-PARTNER-HOOK | Approved | 15 Oct | Blocked by partner sandbox outage | |
| RD-25383 | Deliverable | RISK-035 | Approved | 12 Oct | Verified on the staging build |
Record corrective effort, inspect time-entry validation and compare assigned work with team capacity context.
Approval conditions
| Entry number | Team member | Work date | Hours | Billable | Project | |
|---|---|---|---|---|---|---|
| TE-20083 | Leila Farouk | 13 Oct | 2 | Billable | Reporting dashboard refresh | |
| TE-33931 | Elias Hart | 22 Oct | 10 | Non-Billable | Warehouse mobile rollout | |
| TE-38075 | Nina Okafor | 20 Oct | 4 | Billable | Returns workflow redesign | |
| TE-35896 | Camila Souza | 19 Oct | 7 | Non-Billable | Billing migration verification | |
| TE-33645 | Yuki Tanaka | 19 Oct | 5 | Billable | Warehouse mobile rollout |
Keep unresolved delivery concerns and failed operations visible alongside the defect queue.
Operation receipts
| Receipt number | Operation type | Reference | Occurred at | Result | Notes | |
|---|---|---|---|---|---|---|
| OR-80823 | Project Created | BUILD-2026.10.12 | 21 Oct | Failed | Retest with the October invoice batch | |
| OR-64330 | Work Package Created | TEST-RUN-4812 | 19 Oct | Failed | Awaiting mobile pilot evidence | |
| OR-47399 | Task Created | PR-2841 | 02 Nov | Failed | QA signoff needed before release | |
| OR-58105 | Task Status Changed | QA-REPORT-117 | 19 Oct | Failed | Blocked by partner sandbox outage | |
| OR-91437 | Time Entry Submitted | DEPLOY-2026.10.14 | 02 Nov | Failed | Verified on the staging build |
Defect to verified fix ships ready to use. One step needs a named approval before the work moves on: Verify Fix (QA Engineer).
Record the observed behavior, expected result and project with an accountable owner.
Check severity and the open report before moving it into the triaged queue.
Assign a corrective task within the project work package and record its issue-key reference.
Perform the correction and present the result with the evidence needed for retesting.
Have a QA Engineer independently check the reported behavior before accepting the correction.
Retain the verification evidence and close the accepted defect with task completion checked separately.
Open any project to see its defect reports, the roles that work on it, its process stages and its approvals on one page.
Project name, Organization, Owner and Start date.
Each line is linked to this project.
Delivery Lead, Project Manager and Developer, each with their own permissions.
Set Project Context and Log Defect, with the role that acts.
Verify Fix, with who decides.
Customer portal reliability release · Active
| Issue key | Defect summary | Severity |
|---|---|---|
| BUG-1427 | Duplicate invoice email after retry | Critical |
| BUG-1428 | Scanner freezes after reconnect | High |
| BUG-1429 | Webhook replay creates two tickets | Medium |
QA Engineer assesses severity and checks fixes independently of their implementation. Verification requires the reported behavior and supporting evidence to be reviewed before acceptance.
Signed in as QA Engineer
| Decision | Approver | |
|---|---|---|
| Verify FixHave a QA Engineer independently check the reported behavior before accepting the correction. | QA Engineer | |
| Approve Projects, work packages | Project Manager | |
| Approve defect reports | QA Engineer |
Everyone opens Bug Tracking System to the work that is theirs. Pick a role to see what it starts with.
Maintain delivery organizations and staffing while reviewing project position and supporting evidence.
This is the first screen this role sees.
Time entries · Delivery Lead
| Entry number | Team member | Work date | Hours | Billable | Project | |
|---|---|---|---|---|---|---|
| TE-20083 | Leila Farouk | 13 Oct | 2 | Billable | Reporting dashboard refresh | |
| TE-33931 | Elias Hart | 22 Oct | 10 | Non-Billable | Warehouse mobile rollout | |
| TE-38075 | Nina Okafor | 20 Oct | 4 | Billable | Returns workflow redesign | |
| TE-35896 | Camila Souza | 19 Oct | 7 | Non-Billable | Billing migration verification | |
| TE-33645 | Yuki Tanaka | 19 Oct | 5 | Billable | Warehouse mobile rollout |
Plan work packages, assign corrective tasks and approve delivery acceptance within the assigned project scope.
This is the first screen this role sees.
Time entries · Project Manager
| Entry number | Team member | Work date | Hours | Billable | Project | |
|---|---|---|---|---|---|---|
| TE-20083 | Leila Farouk | 13 Oct | 2 | Billable | Reporting dashboard refresh | |
| TE-33931 | Elias Hart | 22 Oct | 10 | Non-Billable | Warehouse mobile rollout | |
| TE-38075 | Nina Okafor | 20 Oct | 4 | Billable | Returns workflow redesign | |
| TE-35896 | Camila Souza | 19 Oct | 7 | Non-Billable | Billing migration verification | |
| TE-33645 | Yuki Tanaka | 19 Oct | 5 | Billable | Warehouse mobile rollout |
Investigate assigned defects, perform corrective work and record task progress and effort.
This is the first screen this role sees.
Time entries · Developer
| Entry number | Team member | Work date | Hours | Billable | Project | |
|---|---|---|---|---|---|---|
| TE-20083 | Leila Farouk | 13 Oct | 2 | Billable | Reporting dashboard refresh | |
| TE-33931 | Elias Hart | 22 Oct | 10 | Non-Billable | Warehouse mobile rollout | |
| TE-38075 | Nina Okafor | 20 Oct | 4 | Billable | Returns workflow redesign | |
| TE-35896 | Camila Souza | 19 Oct | 7 | Non-Billable | Billing migration verification | |
| TE-33645 | Yuki Tanaka | 19 Oct | 5 | Billable | Warehouse mobile rollout |
Triage reported defects and independently verify fixes using the reported behavior and supporting evidence.
This is the first screen this role sees.
Milestones · QA Engineer
Maintain user access and organization setup without taking over technical verification or delivery acceptance.
Read defect position, corrective effort and delivery exceptions with the underlying records in reach.
This quarter
How far records got this quarter
| Stage | Reached | Step | |
|---|---|---|---|
| Planned | 27 | ||
| Active | 8 | 30% | |
| On hold | 2 | 25% | |
| At risk | 1 | 50% |
Sample totals per stage
Which serious defects remain open, in correction or awaiting verification?
Which project owns each reported problem and who is responsible for the next action?
Which assignees have corrective tasks due, and how should those commitments be read alongside weekly capacity?
How does task effort compare with the work package's expected effort?
Which booked hours are approved, submitted or still being prepared, and which project receives them?
Which pending or missed checkpoints need a delivery discussion?
Which open concerns still need mitigation and an accountable owner?
Which triage or time-entry attempts failed, and what explanation do their receipts provide?
See how Bug Tracking System fits your kind of team.
Connect reported product defects with assigned corrective work and an independent verification decision.
Keep client project defects visible beside work-package dates, checkpoints and recorded corrective effort.
Coordinate defects across internal projects while keeping staffing, risk and verification responsibility clear.
Each stage of defect to verified fix names the role that acts and the status it records, so a change is never anonymous.
Each stage, the role that acts and the status it records
Use Proto to prepare defect handoffs and inspect delivery evidence within your team's permissions.
Set up connections through ERP.AI and Proto workflows, with every change logged.
Every record lives in a table you can see, extend and export. Add fields or whole tables in Proto.
Browse all 13 tablesStart with one team and one process, then add the rest once the basics are running.
Select a representative project, defect and corrective work package. Name the Developer, independent QA Engineer and Project Manager. Agree severity definitions and the evidence needed to accept a correction.
Confirm organization and project records, team members and user access. Resolve the signed-in user’s team membership for personal views and check the projects each person may access.
Load the project and work package before corrective tasks. Keep task project references aligned with their packages. Agree the issue-key convention in task descriptions and resolve attachment and decision references to actual records.
Report and triage the defect, implement the correction and independently verify it. Include a missing-severity failure and a failed retest. Keep the failed result visible while the owner prepares further work.
Submit valid and invalid time entries and inspect the automatic results. Review the milestone, risk and package acceptance separately from the defect. Release the operating process after the team can explain each outcome and access check.
$0per user
The base account and everyday work in the ERP.AI app are free, for every user.
| Usage | Per $1 |
|---|---|
| Record reads (list, filter, get) | 20,000 |
| Search or aggregate queries | 4,000 |
| Record writes | 4,000 |
| Imported or synced records | 200,000 |
| Workflow runs | 2,000 |
| AI agent runs | 2,000 |
| Scheduled jobs or webhooks | 20,000 |
| File uploads (MB) | 2,000 |
| CSV or PDF exports | 100 |
Click Get started, then use Proto to configure Bug Tracking System for your business. Begin with a representative project and defect, a corrective task in its work package and an independent QA Engineer. Rehearse triage, correction and verification before extending the process to the wider team.
Record a useful summary, the project and notes explaining the observed behavior and expected result. Identify the reporter and owner where known, and supply severity before running triage. Keep the issue key available for corrective-task descriptions.
Severity describes the defect's impact. Task priority describes the order in which the team plans to work. QA Engineer assesses severity, while Project Manager uses that context when assigning and sequencing corrective tasks.
The Defect Triage workflow processes an existing Open report with severity present, moves it to Triaged and records a receipt. Missing severity or a report no longer Open produces a failed attempt for investigation.
Put the defect's issue key in the task description and keep both records in the correct project context. Verify that cross-reference when handing the correction to QA so a similar title does not lead to the wrong report.
QA Engineer independently repeats the reported behavior and checks the correction evidence. The defect becomes Verified after acceptance. Retain a failed retest as an unverified result with an explanation for further corrective work.
The Time Entry Approval workflow automatically approves an entry that is still Submitted and has positive hours. It records decision and receipt evidence. Project Manager investigates failures and reviews the effort context; this validation action is separate from human verification of a defect.
Use it alongside the assignee's task dates and estimated effort. Assigned work can span several weeks, so inspect the actual period before treating all assigned estimates as a current-week commitment.
Project Manager assesses the milestone separately against its checkpoint conditions and due date. Record Met or Missed from the actual result. Verification of an individual defect does not automatically complete the milestone or project.
Configure those connections using the issue and task references your team agrees. Retain external run evidence with the intended work, and keep the QA Engineer responsible for independent verification. See connection setup.
Start free, then use Proto to change fields, steps and approvals before your team goes live.