Search Knowledge Base and Documentation

Unknown macro: {kbsearch}
Child pages
  • Bug Fixing Policy

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


  • i9 Technologies Support will help with workarounds and bug reporting.
  • Critical bug fixes will be scheduled according to a variety of considerations, however, are generally addressed by intermediate patch level releases and/or Hotfixes.
  • Non critical bugs will be scheduled according to a variety of considerations, however, are generally addressed by maintenance releases.

Raising a Bug Report

i9 Technologies Support is eager and happy to help verify bugs — we We take pride in it! Please our software and urge your to open a support request in our support system providing as much information as possible about how to replicate the problem you are experiencing. We will replicate the bug to verify, then lodge the report for you. We'll also try to construct workarounds if they're possible.

When raising a new bug, you should include as much detail as possible. 

How i9 Technologies Approaches Bug Fixing

Maintenance (bug fix) releases come out more frequently than major releases and attempt to target the most critical bugs affecting our customers. The notation for a maintenance release is the third dotted final number position in the version (ie the 1 in

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) then it will be fixed in the next maintenance release provided that:


  • 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.

The developers responsible for bug fixing also monitor comments on existing bugs and new bugs submitted in JIRA, so you can provide feedback in this way. 

When considering the priority of a non-critical bug we try to determine a 'value' score for a bug which takes into account the severity of the bug from the customer's perspective, how prevalent the bug is and whether roadmap features may render the bug obsolete. We combine this with a complexity score (i.e. how difficult the bug is). These two dimensions are used when developers self serve from the bug pile.

Further reading

See iSymphony Support Offerings for more support-related information.