Issue Tracking Interface Module for Source Code Event Integration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current issue tracking systems (ITS) and source code management systems (SCM) operate independently, lacking a seamless integration that would enhance collaboration and data management in software development projects.
Innovation Solution
An interface module is introduced to link issues in the ITS with repository events in the SCM, processing data to generate an order of importance for SCM-repository events, which are then displayed alongside issues, providing visual indicators and additional information upon user interaction.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If ITS and SCM operate as separate independent systems, then each system maintains its own functionality and data integrity, but users must switch between systems reducing collaboration efficiency and project visibility
Solution Approach 1:
The patent implements an interface module that acts as an intermediary between the issue tracking system and source code management system. This module receives data from both systems, processes it to generate ordered lists of repository events, and displays them within the issue tracking interface. The intermediary approach enables seamless integration and improved collaboration efficiency without requiring users to switch between systems, while containing integration complexity within the interface module rather than across entire systems.
2Loss of information
If separate systems are used, then system simplicity is maintained, but information silos are created reducing project visibility
Solution Approach 1:
The patent merges the functionality of two separate systems by integrating SCM repository events and ITS issue data into a single unified interface. The interface module combines data from both systems, processes it to create ordered lists, and displays them together within the issue tracking system. This merging eliminates information silos and improves project visibility by making all relevant information accessible in one place, while the integration architecture remains manageable through modular design.
3Productivity
If users switch between separate systems, then data accuracy is maintained, but time is lost reducing productivity
Solution Approach 1:
The interface module performs preliminary actions by proactively receiving and processing data from both the issue tracking system and source code management system before users need it. It continuously monitors both systems, processes incoming data to generate ordered lists of repository events, and makes the integrated information readily available in the issue tracking interface. This eliminates the need for users to manually switch between systems to find related information, thereby reducing system switching time and improving workflow efficiency.
Data Source
AI summary
An issue tracking system (ITS) is disclosed. The ITS comprises a user interface configured to receive user input defining one or more issues and an interface module configured to interface with a source code management system (SCM) and receive from the SCM, data pertaining to linked SCM-repository events. The received data is processed to generate an order for the SCM-repository events to which the issue is linked. A display module is configured to concurrently display a plurality of issues, each issue being displayed with issue information and issues having linked SCM-repository events being displayed with linked SCM-repository event information, said linked SCM-repository event information being displayed according to the generated order.