Version Management System Automates Bug State Synchronization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In software project management, there is a challenge in maintaining synchronized updates between bug management systems and code version control systems, leading to human errors and inefficiencies due to the manual updating of bug states across different systems.

Innovation Solution

A version management system that integrates a code version control system, a bug management system, and an agent system, where the agent system automatically updates bug states and generates branches for code modifications, merging changes into a candidate branch and then to the master branch upon release, thereby reducing human intervention and errors.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual updating of bug states is performed across different systems, then engineers can track and resolve issues, but human errors increase and efficiency decreases

Engineering Contradiction:
Improveaccuracy of bug state updatesVSAvoidefficiency of bug management process
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent merges the bug management system with the code version control system through an agent system. When code is committed to a branch, the agent automatically detects the change, identifies associated bugs, and updates their states synchronously across both systems. This integration eliminates manual updating and ensures consistent state synchronization between bug tracking and code management systems.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The agent system enables self-service automation where the system automatically updates bug states based on code commit events. The agent monitors version control repositories, parses commit messages and code changes, and autonomously updates corresponding bug states without human intervention, reducing both errors and manual workload.

Inventive Principle:
Principle #25Self-service

2Loss of information

If engineers manually update both bug management system and version control system, then comprehensive tracking is achieved, but time consumption increases

Engineering Contradiction:
Improvecompleteness of bug tracking informationVSAvoidtime spent on manual updates
Core Design Contradiction:
Loss of informationVSLoss of time

Solution Approach 1:

The agent system establishes a feedback loop where code commit events trigger automatic bug state updates. The agent continuously monitors the version control system, detects new commits and modifications, and feeds this information back to the bug management system by automatically updating relevant bug states, ensuring information completeness without manual intervention.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system performs preliminary actions by pre-configuring the association between bugs and code branches. When bugs are created or assigned, the agent pre-establishes the linkage to relevant code repositories and branches, so that when code changes occur, the corresponding bug updates can be automatically triggered without requiring manual identification or configuration at update time.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If different systems are updated independently, then system autonomy is maintained, but synchronization between systems deteriorates

Engineering Contradiction:
Improveindependence of system operationsVSAvoidsynchronization of bug state across systems
Core Design Contradiction:
Adaptability or versatilityVSStability of the object's composition

Solution Approach 1:

The agent system serves as an intermediary between the bug management system and the code version control system. It maintains the autonomy of both systems while ensuring synchronization by listening to events from the version control system and translating them into appropriate state updates in the bug management system, acting as a bridge that preserves independence while achieving consistency.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS11175912B2Version management system, version management method and non-transitory computer-readable medium
Publication Date: 2021.11.16 WISTRON CORP
  • US11175912B2 patent drawing
  • US11175912B2 patent drawing
  • US11175912B2 patent drawing

AI summary

A version management method includes the following steps: selecting a master branch; receiving bug information, wherein the bug information includes the bug state; and setting the bug state to a working state after receiving a confirmation assignment message corresponding to the bug information; in response to setting the bug state to the working state, generating a branch corresponding to the bug information based on the master branch, and merging modified code of the branch to a candidate branch; and in response to the release time arriving, merging the candidate branch to the master branch, and setting the bug state to a verification state.