Release Change Analysis Assistant

Problem

Release governance for navigation and service architecture teams often requires the same operational questions: how many releases occurred in a period, which people or modules released the most, and whether changes were fixes, optimizations, AB experiments, or new features. When release data is scattered across Zhiyan approval orders and TAPD requirements, manual review is slow and hard to standardize.

How It Works

• It first extracts time range, query scope, and report level, supporting queries by center, business direction, publisher, change type, or time comparison.
• It calls the Zhiyan API to retrieve approval orders for the selected project_id values, then applies field mapping rules to derive analysis fields.
• For L2/L3 outputs, it generates a structured HTML report covering release cadence, change direction, team contribution, and detailed appendices.
• When Lead Time is requested, it parses TAPD requirement/bug links, queries the created time and final status, and flags cases such as suspected backfill or insufficient permission.

Boundaries

It is scoped to release analysis for the Navigation Technology Center and Service Architecture Center, not a general-purpose release platform. L3 reports require TAPD permission, business-direction queries can depend on the static mapping table, and filters using plm_filter may exclude approval order types that do not contain a plm_app field.