Session Identifier for Automated Issue Report Population
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional issue tracking systems are time and resource-consuming, leading users, especially quality control engineers, to prefer abstract and terse issue reports, making it difficult to accurately track issues when interacting with these systems, especially on mobile devices.
Innovation Solution
An issue tracking system that generates a session identifier to tag debugging information, allowing automatic population of issue report templates with relevant data, such as screenshots, crash reports, and logs, reducing the need for manual data entry and enhancing report detail.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If users manually input information to issue tracking systems, then issue reports can be detailed and accurate, but the process is time-consuming and resource-consuming
Solution Approach 1:
The system performs preliminary actions by automatically collecting debug data, generating session identifiers, and populating issue report templates with relevant information before the user submits the report. This pre-population reduces the manual data entry required while maintaining comprehensive and accurate issue reports.
Solution Approach 2:
The issue tracking system performs self-service by automatically gathering debug information from the application under test, tagging it with session identifiers, and populating report templates without requiring manual intervention. The system serves itself by automating the data collection and report generation process.
2Productivity
If users interact minimally with issue tracking systems, then time and resources are saved, but issue reports become abstract and undetailed
Solution Approach 1:
The system implements feedback by automatically collecting debug data from the application under test during the debugging session, tagging it with session identifiers, and using this feedback information to automatically populate issue report templates. This ensures detailed and accurate reports are generated with minimal user interaction.
Solution Approach 2:
The session identifier acts as an intermediary that links the debugging session to the collected debug data and ultimately to the issue report template. This intermediary mechanism enables automatic population of detailed reports without requiring direct user input, maintaining both efficiency and information completeness.
3Ease of operation
If automatic population of issue reports is implemented, then time and effort are reduced, but system complexity increases
Solution Approach 1:
The system segments the issue reporting process into distinct components: session identifier generation, debug data collection and tagging, template selection, and automatic population. This segmentation allows each component to be handled independently, reducing the perceived complexity for users while maintaining automated functionality.
Data Source
AI summary
An issue tracking system includes a host device executing an issue tracking service in communication with a client device executing at least one of an issue reporting application and/or an application under test. The issue reporting application generates a session identifier that defines a debugging session. The application under test can receive the identifier and tag logs or other data generated during the debugging session. The issue reporting application can thereafter receive the debugging data and can populate an issue report template based on that data.