Bug/Enhancement Reporting

<< Click to Display Table of Contents >>

Navigation:  Support Services >

Bug/Enhancement Reporting

MasterLink Shop Writer was originally developed in 1982 from direct, hands-on service shop experience. Since that time, the system has continued to evolve based on:

•Real world shop operations

•Observations from daily business use

•Technological advancements

•Suggestions and feedback from actual service professionals

The continuing development of MLS depends heavily upon communication with the people who use the system every day. For this reason, MasterLink Software strongly encourages users to report:

•Program bugs

•Unexpected behavior

•Workflow concerns

•Operational suggestions

•New feature ideas

•Enhancement requests

Many of the features currently built into MLS originated directly from user recommendations.


Accessing The Reporting Utility

Under the Tools menu you will find the:

Bug / Enhancement Report

option.

Selecting this utility automatically prepares an email message to MasterLink Software technical support.

This should always be the preferred method for reporting:

•Program failures

•Error messages

•System crashes

•Operational inconsistencies

•Suggested improvements


Why This Utility Is Important

The reporting utility automatically includes:

•Error log information

•Internal diagnostic data

•System status details

•Program location references

This information allows MasterLink Software to quickly identify:

•Where the issue occurred

•What process was active

•What conditions caused the failure

•How to reproduce and correct the problem

In many cases, the attached log information pinpoints the exact cause immediately.


Always Report From The Affected Workstation

If possible, submit the report directly from the computer where the problem occurred.

This is important because:

•The local error logs are attached automatically

•Workstation-specific configuration details are preserved

•Network references remain accurate

•Device-specific conflicts can be identified

Submitting from another workstation may omit critical diagnostic information.


Completing The Report Properly

Subject Line

In the email subject field, identify:

•The program area involved

•The task being performed

Examples:

•Workorders – Printing Invoice

•Inventory – Parts Lookup

•Accounts Receivable – Statement Printing

This helps support personnel immediately route and prioritize the issue.


Description Area

Provide as much detail as possible about:

•What you were doing

•What buttons were pressed

•What screen was active

•What happened before the error occurred

•Whether the issue can be repeated

Even small details can help identify the exact cause.


Bug Repairs Are High Priority

Program failures and operational bugs are treated with the highest priority by MasterLink Software.

Because MLS includes automated internet updating:

•Corrections can often be distributed immediately

•Fixes may be available within hours

•Updated files can download automatically to authorized systems

MasterLink Software does not believe users should “live with” software bugs any longer than necessary.


Enhancement Requests

Suggestions for improving the system are always welcome.

Enhancement ideas often come from:

•Service writers

•Technicians

•Managers

•Owners

•Accountants

•Multi-location operators

Because these users work with the software daily, their observations frequently lead to valuable improvements in:

•Workflow speed

•Reporting

•Automation

•Screen design

•Customer communication

•Accounting integration

Many MLS features exist today because a user took the time to suggest them.


Best Practices

Report Problems Immediately

Do not wait until:

•You forget the details

•The issue becomes harder to reproduce

•Multiple workstations are affected

Immediate reporting improves repair speed significantly.


Be Specific

The more information you provide:

•The faster the repair

•The easier the diagnosis

•The more accurate the correction


Never Assume “Someone Else Already Reported It”

Even repeated reports are useful because they:

•Confirm reproducibility

•Show severity

•Reveal patterns

•Identify affected versions


Development Philosophy

MasterLink Shop Writer continues to evolve because of the partnership between:

•Real world service professionals

•Experienced software developers

•Ongoing communication between both groups

The Bug / Enhancement Reporting utility is one of the most important tools in maintaining that relationship and continuously improving MLS for everyone.