Questions, answered

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.