Guide to Issue Tracking

Issue Tracker

CCNx is using a Redmine Issue Tracker to keep track of bugs and feature requests.

  • Anyone may read or search the bug database without logging in, but in order add new issues you'll need to have a Redmine account.  If you do not have one, go ahead and create a new Redmine account but please use the same user name that you use on rest of the ccnx.org site (if you have one).  We apologize for the inconvenience caused by the fact that Redmine has a separate account database.
  • As a general primer on bug filing, and to provide information vital to diagnosing the problem, we suggest you read the Bug Filing Guidelines.
  • Once filed, you will receive an email about your new bug.  You will continue to receive bug status changes through the life of the bug.
  • If you have found the bug to exist already, that's ok. There is still a chance for you to provide some seriously helpful feedback on the bug state.  Frequently, bugs will get closed by Core developers because they are duplicate, marked as won't fix, works for me, or need-more-info.  Frustrating as this can be to users and developers, bugs must go through a triage.  If you feel there is something you can add to the dialogue around a specific bug, please chime in.  Add a description of your specific issues.  Chiming in with a "me too" is fine, but even more useful is to add something to the discussion.  "Why was this bug closed as fixed when I can still reproduce it?"  "When will this get assigned and fixed?"  etc.  
  • Has your bug been fixed?  Are you getting proper feedback from the Core dev team.  If you feel you aren't being heard, feel free to take the discussion onto the mailing list to escalate.  Frequently bugs are fixed to support specific release goals, and so bugs existing outside of core project goals may see deprioritization.
Bookmark/Search this post with: