Bug Tracking

Toodle uses Jira to record defects, usability issues and improvements identified during development and testing. The tracker helps the team prioritise problems, assign responsibility and follow fixes through to completion.

Bug Tracker

Resource	Description
Toodle Jira Board	Team issue tracker used to manage bugs and improvements
Jira Export	A static export of the issue tracker is included in the project evidence for reviewers who cannot access the private Jira board
In-app Problem Reporting	Authenticated users can report problems through Report a Problem in the application

Issue Tracking Process

Issues were identified through user feedback sessions, stakeholder discussions, application testing and in-app problem reports.

Each issue was recorded with relevant details, including:

• A clear title and description.
• The affected page or workflow.
• Expected and actual behaviour.
• Reproduction steps where applicable.
• Priority and assigned team member.
• Supporting screenshots or evidence where available.
• Implementation and verification details.

Bug Resolution Workflow

The team followed a straightforward issue-resolution process:

1. Identify: Record the issue and its impact.
2. Prioritise: Determine its severity and assign responsibility.
3. Implement: Address the issue through the normal development workflow.
4. Test: Verify the affected functionality and check for regressions.
5. Close: Update the Jira issue once the team considers the work completed.

The Jira board used To Do, In Progress and Done to track progress.

Issue Tracking Results

The Jira export dated 11 October 2026 contains 21 issues, all recorded with a status of Done.

These records include bugs, usability improvements and development tasks. A Done status represents the issue's recorded completion in Jira and does not, by itself, establish that an independent retest was performed.

The tracker includes findings related to:

• Authentication and account access.
• Application onboarding and navigation.
• Allocation and session-swap workflows.
• Mobile responsiveness and notifications.
• Dark mode and interface consistency.
• Profile and reporting functionality.

These findings informed improvements made throughout development.

Verification and Evidence

Where applicable, issues were linked to implementation work and checked after changes were made.

Supporting evidence includes the Jira issue history, user feedback records, application tests and relevant pull requests.

The team's wider feedback process is documented under User Feedback & Usability.