These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Bug Tracking System
- Data Model
The tables behind Bug Tracking System
Bug Tracking System ships with 13 tables, grouped here by the feature that uses them. Every record your team works with lives in one of them, and you can add fields and tables in Proto.
- Tables
- 13
- Features
- 6, plus shared settings
- Change it
- Add fields and tables in Proto
How the model is organised
Defect Intake and Triage
Defect reports references Projects and team members through Project, reported by and Owner. Severity and Status describe the reported problem and its lifecycle.
Fix Delivery
Projects contains work packages through work packages.Project. Tasks references its required work package, optional Project and Assignee. The task and its package should resolve to the same project.
Verification and Evidence
Record attachments uses parent table name and parent record ID for text-based parent resolution. Review decisions uses subject type and subject reference, plus related project and Reviewer.
Projects and Milestones
Projects references Organizations and an owning team members record. Milestones references Projects and Owner and carries its due date and Status.
Time and Capacity
Time entries references team members and Projects, with an optional Task. Team members carries weekly capacity hours and assignment-related totals.
Risks and Oversight
Risks references Project and Owner. Operation receipts records operation type, Reference, Result and Actor. Resolve Reference to the source record using the convention for that operation type.
Every table, by feature
- Defect Intake and Triage5
- Fix Delivery5
- Verification and Evidence6
- Projects and Milestones7
- Time and Capacity6
- Risks and Oversight7
- Shared and settings1
- Defect reports
Defects raised against project work, tracked from Open through triage, fix and independent verification.
Linked to Projects, Team members - Projects
Engagements delivered for an organization, with budget and schedule.
Linked to Organizations, Team members - Team members
Delivery staff with role, practice and weekly capacity.
- Tasks
Individual pieces of work assigned to a delivery team member.
Linked to Work packages, Team members, Projects - Operation receipts
Evidence that a delivery operation was executed.
Linked to Team members
- Tasks
Individual pieces of work assigned to a delivery team member.
Linked to Work packages, Team members, Projects - Work packages
Groupings of work inside a project.
Linked to Projects, Team members - Projects
Engagements delivered for an organization, with budget and schedule.
Linked to Organizations, Team members - Defect reports
Defects raised against project work, tracked from Open through triage, fix and independent verification.
Linked to Projects, Team members - Team members
Delivery staff with role, practice and weekly capacity.
- Defect reports
Defects raised against project work, tracked from Open through triage, fix and independent verification.
Linked to Projects, Team members - Tasks
Individual pieces of work assigned to a delivery team member.
Linked to Work packages, Team members, Projects - Record attachments
Files attached to delivery records.
Linked to Team members - Review decisions
Recorded approval decisions on delivery subjects.
Linked to Team members, Projects - Projects
Engagements delivered for an organization, with budget and schedule.
Linked to Organizations, Team members - Team members
Delivery staff with role, practice and weekly capacity.
- Projects
Engagements delivered for an organization, with budget and schedule.
Linked to Organizations, Team members - Organizations
Client and internal business organizations that projects are delivered for.
- Work packages
Groupings of work inside a project.
Linked to Projects, Team members - Tasks
Individual pieces of work assigned to a delivery team member.
Linked to Work packages, Team members, Projects - Milestones
Dated checkpoints a project must meet.
Linked to Projects, Team members - Defect reports
Defects raised against project work, tracked from Open through triage, fix and independent verification.
Linked to Projects, Team members - Review decisions
Recorded approval decisions on delivery subjects.
Linked to Team members, Projects
- Time entries
Hours booked by a team member against a task and project.
Linked to Team members, Projects, Tasks - Tasks
Individual pieces of work assigned to a delivery team member.
Linked to Work packages, Team members, Projects - Projects
Engagements delivered for an organization, with budget and schedule.
Linked to Organizations, Team members - Team members
Delivery staff with role, practice and weekly capacity.
- Review decisions
Recorded approval decisions on delivery subjects.
Linked to Team members, Projects - Operation receipts
Evidence that a delivery operation was executed.
Linked to Team members
- Risks
Project risks with probability, impact, owner and mitigation.
Linked to Projects, Team members - Projects
Engagements delivered for an organization, with budget and schedule.
Linked to Organizations, Team members - Milestones
Dated checkpoints a project must meet.
Linked to Projects, Team members - Operation receipts
Evidence that a delivery operation was executed.
Linked to Team members - Defect reports
Defects raised against project work, tracked from Open through triage, fix and independent verification.
Linked to Projects, Team members - Time entries
Hours booked by a team member against a task and project.
Linked to Team members, Projects, Tasks - Team members
Delivery staff with role, practice and weekly capacity.
Keys and references
Keep business identifiers such as issue key, project code, package code and task key distinct from the identifiers used by text-based parent fields. Resolve parent record ID and subject reference using the agreed mapping for the actual target record. Record attachments.parent table name includes the label Issues; agree and test its mapping to defect reports before attaching defect evidence. Preserve the existing select values.
Include the defect’s issue key in Tasks.Description. At the QA handoff, resolve that key to the intended defect reports record and check that both records belong to the same project.
Establish a verified mapping from each signed-in user to the intended team members record before enabling personal views. Use Email to help reconcile identities, and confirm each match during access setup. Users.User is a self-reference. A job label in team members.Role and a permission role assigned to a user serve different purposes.
Review decisions.subject type supports Project, Work Package, Task, Milestone and Deliverable. Use an actual Task subject for corrective-task acceptance. Time-entry workflow decisions require their configured subject-reference convention to be checked during setup. Calculated fields such as hours variance and risk score are stored as text; confirm their calculation and formatting before treating them as numeric report inputs.
Migration order
- Establish Users, Organizations and team members with the intended identity mapping and access scope.
- Load Projects with the correct organization and owner references.
- Create work packages, then Tasks with matching project context and assignees.
- Load defect reports, Milestones and Risks with project links and accountable owners.
- Link time entries to their team members, projects and optional tasks, preserving dates and result states.
- Resolve attachment parents, review subjects and operation references explicitly before loading supporting evidence.
Set up Bug Tracking System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.