Design and Implementation of an Integrated Case and Bug Management Platform (Todolist) for Agile QA Processes

1. Introduction

With the accelerating pace of internet development, traditional case and bug management processes can no longer meet rapid‑iteration scenarios. By analyzing and optimizing the workflow, strengthening interaction, and emphasizing data recording and analysis, a new integrated Case and Bug management system—Todolist—was created.

2. Problems Identified

Typical project development flow contains many manual interventions and information distortion, leading to issues such as difficulty enforcing test‑submission standards, challenges in applying reject criteria, developers waiting for test cases, and outdated case creation by PMs.

2.1 Project‑process issues

a. Test‑submission standards are hard to enforce because new developers often skip or incompletely run cases without an efficient platform to record self‑testing.

b. Reject standards are hard to apply; risk‑related rejections are delayed due to manual reporting.

c. Developers frequently finish coding before test cases are written, causing bottlenecks.

d. PM‑written cases may become obsolete after checklist review.

2.2 User‑experience issues

a. Checklist and case are not directly linked, relying on memory and causing inconsistencies.

b. Existing case/bug tools are slow, complex, and lack real‑time statistics, making it hard to obtain accurate data.

3. Improvement Plan

3.1 Process Improvements

a. Automatic enforcement of test‑submission standards by monitoring case execution and code coverage.

b. Automatic detection and notification of reject‑rule violations during testing.

c. Checklist‑missing reminders to prompt QA to write cases promptly.

d. Automatic case generation from checklist (mind‑map) to eliminate manual effort.

Note: Direct conversion may miss standard case elements; users should consider adding preconditions, steps, and expected results manually.

3.2 User‑Experience Enhancements

By analyzing peer products, the platform adopts a minimalist approach, retaining only core functions, simplifying interactions, and providing multiple entry points (PC, Touch, APP, bots). Checklist elements are merged into cases, templates are used for quick creation, and a clean UI encourages adoption.

4. Platform Architecture

The system consists of four functional modules: external integration, Checklist‑to‑Case, Case management, Bug management, and an analytics/statistics layer. Integration with Jira is achieved via embedded Java backend service (qodin) and React frontend service (easypmo), leveraging Jira’s plugin capability and Redis for cross‑device image transfer.

Key components include:

Jira as the entry point for PM, RD, and QA.

Embedded services (Java backend, React frontend) for minimal code intrusion.

Checklist authoring based on the kityMinder open‑source framework, enhanced with Jira linkage, priority sync, and case/bug operations.

Open APIs for quality analysis, bug statistics, and test progress data.

Case and bug platforms (Todolist) that auto‑generate cases from checklist leaf nodes and streamline bug reporting.

Configurable feature switches, guides, and permission controls for tailored user experiences.

5. Platform Demonstration

The demo showcases integrated entry points, checklist creation, case operation pages, bug operation pages, and statistical dashboards, illustrating how the platform consolidates all QA workflow steps within Jira while providing a lightweight, automated, and data‑driven environment.