CRM Together - Bug Fixing Policy

--Our Support team will help with workarounds and bug reporting. --We'll generally fix critical bugs in the next maintenance release. --We schedule non-critical bugs according to a variety of considerations.

We are keen to help verify bugs and resolve as quickly as possible. Create an issue in our Customer 365 portal or email an issue providing as much information as you can about how to replicate the problem you're experiencing. We'll replicate the bug to verify and then report to you. We will also try to provide workarounds if at all possible.

Maintenance (bug fix) releases attempt to target the most critical bugs affecting customers. The notation for a maintenance release is the final number in the version (EG 1 in 4.5.1). Details of releases are here http://accelerator.crmtogether.com/index.php/Releases If a bug is critical (production application down or major malfunction causing business revenue loss or high numbers of staff unable to perform their normal functions) we'll fix it in the next maintenance release, provided that: --The fix is technically feasible (it doesn't require a major architectural change) --It doesn't impact the quality or integrity of a product For non-critical bugs we prioritize the bug according to these factors: --How many of our supported configurations are affected by the problem --Whether there is an effective workaround or patch --How difficult the issue is to fix --Whether many bugs in one area can be fixed at one time We take into account the severity of the bug from a customers' perspective and how prevalent the bug is and whether new features on our road-map may render the bug obsolete. We also consider the complexity (how difficult the bug is) when selecting issues to work on.