Browse Prior Art Database

Enhanced Bug Reporting with User Input and Automation of Information-Gathering

IP.com Disclosure Number: IPCOM000131918D
Publication Date: 2005-Nov-21
Document File: 3 page(s) / 16K

Publishing Venue

The IP.com Prior Art Database

Abstract

This invention deals with problems in reporting bugs from a PDA, specifically: 1. user describing the bug, and sending the bug report to engineering; 2. manually gathering info on the device and its software to include with the report; 3. manually gathering supplementary information such as debug logs, e-screens, other emails, and info that will assist engineering, and later sending that information; 4. having to send the bug report from a PC.

This text was extracted from a Microsoft Word document.
This is the abbreviated version, containing approximately 46% of the total text.

Enhanced bug Reporting

Enhanced Bug Reporting with User Input and Automation of Information-Gathering

Disclosed Anonymously

This invention deals with problems in reporting bugs from a PDA, specifically:

 1. user describing the bug, and sending the bug report to engineering;

 2. manually gathering info on the device and its software to include with the report;

 3. manually gathering supplementary information such as debug logs, e-screens, other emails, and info that will assist engineering, and later sending that information;

 4. having to send the bug report from a PC.

The invention includes a new application in the PDA (or possibly added to the current debug log), that:

 1, when activated (prompted) by the user or by unusual event on the device, calls up a bug report email form, with

     a. outline of information that the user fills in describing the bug. The outline is detailed enough to cover expected bugs

     b. automatic inclusion of information (so that the user does not have to manually add it) on the:

            i.    device (model, PIN, IMEI or ESN,…)

            ii    SIM (Operator, IMSI, mobile number,…SIM characteristics,…) or subscription or lack of a SIM (in which case the bug report is prepared and stored since it cannot be sent.)

            iii.  device software (version, date, ) and application software (type, version,…)

            iv.   situation (location, network the device is connected to or was last connected to, GPS or other geographic location, band the device was operating in,…)

            v. message identity of the last debug log and the last bug report (this message)

            vi. standard information that is sent with the debug log

     c. additional information, including:

            i.   information that is automatically triggered by the activation or by the user, such as version number of an application (when the user identifies the application in the first part of the bug report), and / or appropriate engineering screens (for example when "unable to get pdp context" is checked,

             ii.  information that the user requests such as particular e-screen when the problem is not listed in the bug list, and the user knows what information may be helpful in identifying the bug or problem

    

The user no longer has to search for other messages (debug log,…) and send them in separately to be later associated with the trouble report by the group receiving them.

The information may be sent either in the bug report message, or may be sent as a bug report plus another message(s) with additional information. The bug report contains the identity of the message(s) with additional information, if there are any. The e-mail server may merge the two messages or include the additional information messages as "attached messages", so that the recipient has _all_ available information.

...