Integrating TAPD with DingTalk via a Chrome Extension for Real-Time Bug Notifications

Background

The company uses TAPD for project, test case, and defect management, while DingTalk is the internal communication tool. TAPD and DingTalk do not integrate well, so when a bug or task status changes, timely notification to relevant colleagues is needed.

Solution

A Chrome extension is developed to listen to the status of tasks and bugs of interest. When a status transition occurs, the extension calls a DingTalk robot to instantly notify the appropriate workgroup.

Current Effect

For bugs with severity ≥ Severe and priority ≥ High, the average time to reach the "Resolved" state dropped from 4.8 hours to 2.9 hours, greatly improving bug‑fix and testing efficiency.

Principle

The extension is written in JavaScript. It monitors button clicks and field changes, and when conditions are met it uses XMLHttpRequest to send a message to a pre‑configured DingTalk group robot, achieving the effect shown above.

Code

Tips: The plugin encapsulates an API that retrieves TAPD users' phone numbers so that the DingTalk robot can @‑mention specific people. If you prefer not to use the API, you can store the mapping in a simple JavaScript Map . If @‑mentions are not required, the phone‑number lookup can be omitted.

After writing the script, package it as a Chrome extension. Below is the overall file structure and installation process.

Plugin File Structure

Installation Steps

Unzip the plugin package.

Open Chrome → Extensions.

Load the unpacked extension.

Ensure the extension is enabled.

Add the group robot to the DingTalk group where notifications should be sent.

Summary

This article provides a practical approach to creating a Chrome extension that synchronizes TAPD bug status with DingTalk notifications; the concept can be extended to monitor other entities as needed.