Hi,

This is an explanation of how we triage bug reports and what some of the changes we make to a thread's title mean.

Whenever a new Bug Report is posted in this forum, we have code in vBulletin that sends the bug report to our internal change management system(JIRA).

At this point the bug is held in a waiting area until a Zen Cart Dev can look at it. We may ask further questions within the thread to try and determine whether the problem is actually related to a problem in Zen Cart code, or if it has some other resolution. (e.g. it's really a feature request, or its down to a misconfiguration or maybe its a duplicate of a previous report)

If we feel that the bug is genuine, we will then triage the bug to decide when/how we are going to fix it. This depends a lot on how we feel it affects the Zen Cart community as a whole. e.g. if it is a bug that only affects a small minority, we may post a fix on the forum, and schedule an internal fix for a future version, not necessarily the next release.

If we feel the bug needs addressing, it will be progressed within our change management, and assigned to a release version (and possibly at this point assigned to a particular person) and at that point it will be given a CHANGE-xxx identification.


Thread Title Prefixes which you might see, and what they mean:

  • [UNDER REVIEW] This means we are actively testing the bug, but have not accepted it yet for fixing.
  • [OPEN CHANGE-XXX] We have accepted the bug as genuine and are determining how to address
  • [INPROGRESS CHANGE-XXX] generally means that it has been assigned to be fixed in the next release, and has also been assigned to a Dev
  • [Fixed {version}] We have committed a fix to our internal GIT repo.
    (And if the {version} is 1.5.x or later then you can find the fix in our github.com repository, even if the version has not been released yet. We may also post within the thread a link to the exact fix at github.com)
    AND if the {version} has been officially released, then that {version} ALREADY contains the fix for the issue mentioned.


For more information regarding our github repo please see github.com/zencart
and also http://www.zen-cart.com/showthread.p...Hub-Repository

NOTE: On GitHub, you may notice that the newer "issues" don't contain any of these "CHANGE-XXX" prefixes ... this is because each code-change put on GitHub (called a PR or Pull Request) has its own number assigned instead.