Reposting an old article (2014) because the Adobe ColdFusion Tracker still lacks professional oversight and management.

If you take a look at the ColdFusion Bug Report you will see the following “States”:

  • Deferred
  • Fixed
  • Needs Review
  • Never Fix
  • To Defer
  • To Fix
  • To Test
  • To Track
  • Unverified
  • Withdrawn

The states can either have a status of open or closed.

Like most large organizations, metrics that can be easily used to show progress are often misused to make people look good (just ask the VA). This would appear (perception is reality) to be the case here as well.  While I know Adobe has internal processes and I don’t want to second guess them, it is apparent that the metric that matters is the number closed (Fixed + Deferred + Never Fix + Withdrawn).   I for one can’t fathom the concept that a deferred bug is closed.  It is not closed.  Unless this is a formal way of ignoring bugs (perception), it is open and you have chosen to delay resolution until some future date or version.  Also, the Fixed status is confusing as bugs are marked as fixed, but there is no indication how or which update/hotfix solved the issue.  My recommendation to alleviate the public perception and to help clarify the true status of bugs would be to add the following categories:

  • Deferred – Add Version Target (e.g. Deferred – CF12)
    Leave it as Open and once a deferred bug is set for resolution, move it to the appropriate state (e.g. To Fix, To Test, etc.).
  • Fixed – Pending Update
  • Fixed – Update Posted
    Add a comment or separate field that shows which update or hotfix resolved this issue.

The metric used for success should be Fixed – Update Posted. 

While I know this won’t solve everybody’s concerns, or scenario (bugs that are re-deferred to another version) I think it would be a move in the right direction.’

Featured image by Evan Kirby