What to Expect When You Report a Software Issue
We constantly strive to improve the software; input from you and dealers like you help us make our products better for you and for all the other dealers who use them. This page describes how to report a software issue, and what happens afterward.
How to Report a Software Issue
There are four types of issues typically reported:
| Issue Type |
Definition |
Defect |
A feature or procedure in existing software that is defective, does not work as designed, or creates faulty results and must be corrected |
Design Flaw |
A feature or procedure in existing software that creates an issue that was not considered in the original design, and must be redesigned, even if it works as it was originally designed |
Enhancement |
A new feature, application, field, view, report, or other functionality that does not yet exist in released software |
Project |
A request for custom development |
To report a software defect, design flaw, or enhancement, contact your support team.
To ensure your company gets the appropriate software update and related communications, make sure your company is attached to the issue record in our system, and you will get the QC (DevTrack) ID.
As always, you can contact support four ways:
To request a custom development project, please contact Dean Kim.
Other industry- and product-specific sales contact information is on eci2.com.
Issue Validation
Each reported issue must be triaged or reviewed for the following purposes:
| Purpose |
Definition |
Duplicate Reports |
Another customer may have previously reported your issue. If this is the case, we will link the duplicate issue report with the existing report, and close the duplicate. We will ensure that you automatically receive the software release that includes the change(s) you requested. |
More Information Needed |
A Support tech will contact you if we need more information from you, for instance to clarify the issue or obtain steps, parameters, data, examples, or other information necessary to duplicate a problem. |
Invalid Issues |
If the reported feature or function works as it was originally designed, or if the problem cannot be duplicated, the issue will be closed. Support techs are notified if the issues they submitted were closed, and so are any customer(s) who reported the issue. |
Workaround Available |
If we have a way to resolve a problem without programming, a Support tech will contact you. You have the opportunity to close the issue at this point. |
Issue Prioritization
Issues will be prioritized based in part on the severity of their affect on dealers:
| Severity |
Definition |
System Down |
The dealer cannot complete orders or conduct business. If this is the case, appropriate managers are automatically notified and work begins immediately to resolve the issue. |
Severe Impact |
Critical functionality is broken or missing, many dealers are affected, and/or the workaround is excessive. (Examples: A broken function affects a great number of dealers who use it daily. Or, an available workaround adds several steps that extend the amount of time to process each order.) |
Medium Impact |
A broken or missing function impacts business but perhaps a reasonable workaround is available. (Example: data does not appear as expected in one application but is accessible through another commonly used application.) |
Minor Impact |
The feature is used infrequently, or the problem does not impede a dealer's workflow, or a typographical error does not affect money. (Example: The default cursor focus or tab sequence in an application requires some simple Shift-Tabbing or one or two extra clicks for most dealers.) |
Software Development & Testing
Prioritized issues will be placed on a list in the order they should be addressed, and may at that time have a target release version. As programmers complete each software change on the prioritized issues list, quality assurance is notified. As each software change assigned to a planned software release has passed testing, the issue is closed for release.
Software Release
We will ensure that you receive the software release that includes the change(s) you requested. Our standard shipping method for most software releases is UPS Ground. If the issue is severe, other release methods may be used. Software releases with major enhancements will be announced via email.
Other Resources
As always, the following resources are available for additional information:
- Release Notes. Always check here for important information you may need to know prior to loading a software update.
- Software Updates. View, print, or download detailed instructions on how to install our software updates.
- Program Updates. You can query every software change made to DDMS products, starting with the most recent changes.
- Mass Emails. You can review copies of the principal mass emails from ECI² Technical Support in the last few months.
|