07. Defect tracking Report - khalillabban/Snorting-Code GitHub Wiki
Defect Tracking Report
This section documents all defects identified throughout the development process. Bug reports are organized by release and sprint, with direct links to their corresponding GitHub issues.
Bug issues can have the following prefixes:
BUG-#.#: task-specific bugs where#.#represents the specific user story in which the bug was produced. (e.g., app crashes when getting outdoor directions to and from the same building)BUG-UI: user interface bugs that can't be associated to a specific task (e.g., issues with layout, spacing, styling).BUG-GEN: general system bugs regarding logic, architecture, or cross-cutting issues (e.g., app freezes when returning to previous page)
To view all bug issues, use the following filter:
is:issue label:bug
Bug Report Format
Each bug report must include the following elements.
Screenshot(s)
Include if applicable.
Environment & Impact
This section captures all contextual and severity‑related metadata for the defect.
- Area
- Severity
- Frequency
- Platform
- Device
- Affected Version
- Endpoint (if applicable)
- Request Details (if applicable)
Summary
A concise description of the defect and its impact.
Steps to Reproduce
Enumerate the actions needed to trigger the defect.
Expected Behaviour
Describe what should have happened.
Actual Behaviour
Describe what actually happened.
Implementation Notes (optional)
Developer-only notes summarizing root cause, relevant code areas, and any follow‑up considerations.
Example Format:
Release 1
Sprint 1
No bugs were reported during this sprint.
Sprint 2
Bug Report – UI / Map Display Issues
BUG-UI: Fix building boundaries
Sprint 2 Summary
Sprint 2 primarily revealed minor UI-related issues rather than functional defects. The reported bug focused on visual inconsistencies within the campus map, which, while not blocking functionality, impacted the overall polish and readability of the interface. These types of issues were considered low priority but important for improving user experience in later iterations.
Release 2
Sprint 3
Bug Report – Search / Navigation Behavior Issue
BUG-GEN: Debugger for user location
Bug Report – Missing Test Artifacts in Workflow
BUG-GEN: Jest testing information insufficient
Sprint 3 Summary
Sprint 3 introduced both core functionality and development infrastructure issues. While the navigation and search bug impacted user location tracking and required critical debugging, the missing test artifacts issue was more technical in nature but still essential for maintaining long-term project auditability and testing transparency. Overall, this sprint highlighted the need for tighter integration between front-end functional components and the automated workflows supporting the development lifecycle.
Sprint 4
No bugs were reported during this sprint.
Release 3
Sprint 5
Bug Report – Map Interaction Issue
BUG-UI: Fix visual styling for start and end destination pins
Bug Report – Indoor Navigation Issues
BUG-4.2: Fix indoor time calculation
BUG-4.2: Fix indoor cross-floor travel detour
Sprint 5 Summary
Sprint 5 introduced both visual interface and complex navigational logic issues. While the styling of destination pins impacted immediate map interaction and user clarity, the indoor navigation bugs regarding time calculations and cross-floor detours were more technical in nature but still essential for providing reliable routing in multi-level environments. Overall, this sprint highlighted the need for tighter integration between user-facing map elements and the underlying accuracy of indoor pathfinding algorithms.
Sprint 6
Bug Report – Next Class & Feature Logic Issues
BUG-3.2: "Next Class" room parsing fails for complex room numbers (MB-S2.330)
BUG-3.3: Next Class navigation bar does not trigger indoor navigation
Bug Report – Indoor Navigation & Asset Data Issues
BUG-4.2: Fix indoor navigation overlay for buildings MB and VL
BUG-4.2: Missing elevator node and edges for Hall Building Floor 1
Bug Report – Routing State & Transition Issues
BUG-4.7: Accessible toggle state resets during multi-segment trips
BUG-4.8: Navigation button disabled after indoor-to-outdoor travel
Bug Report – UI Layout & Transit Feedback Issues
BUG-UI: Add padding on Android to avoid content overlap with navigation bar
BUG-UI: Transit button remains active when shuttle is unavailable
BUG-UI: Insufficient detail for Transit options
BUG-UI: Outdoor POI bugs - navigation strategy and unintuitive behavior
Bug Report – Usability Improvements Issues
BUG-UI: Leftover Set as my location demo button in building popup
BUG-UI: Fix building label coordinates
BUG-UI: Can't access the Get direction button for the Next class Navigation Page
BUG-UI: Can't zoom in the indoor map
BUG-GEN: Rigid way to type the name of the class room
BUG-UI: Indoor navigation room search does not show autocomplete suggestions
BUG-UI: Direction steps panel blocks part of the active route
BUG-UI: Able to see the the time and distance on the navigation step panel
BUG-UI: Preview of all times of transportation options at the same time
BUG-UI: Take out the by default current location as the start point
BUG-UI: Change outdoor POI button icon to more intuitive
Sprint 6 Summary
Sprint 6 focused on improving the user experience and fixing navigation logic. Updates to icons, autocomplete, and zoom controls reduced user friction. However, bugs in room parsing and state persistence showed that indoor and outdoor transitions still need stabilization. This sprint highlighted the difficulty of a seamless experience. As the project matures, the focus moves from basic features to the reliability of the total journey across campuses and transport modes.