ChiliProject is not maintained anymore. Please be advised that there will be no more updates.

We do not recommend that you setup new ChiliProject instances and we urge all existing users to migrate their data to a maintained system, e.g. Redmine. We will provide a migration script later. In the meantime, you can use the instructions by Christian Daehn.

Bug report helper (Feature #134)

Added by Derek Montgomery at 2011-02-03 12:10 pm. Updated at 2011-05-27 11:59 am.

Status:Open Start date:2011-02-03
Priority:Normal Due date:
Assignee:Holger Just % Done:


Target version:-
Remote issue URL: Affected version:


In the Settings of CP, under Information, you should add a new item: Troubleshooting.
It would contain most of the required information needed to properly open a bug on CP tbug tracker:
  • ChiliProject version or revision and where you got it from (Examples: tag 1.1.0 from git, Debian package version 1.1.0)
  • Ruby version (Example: 1.8.7)
  • Rails version (Example: 2.3.5)
  • Database including version if that is possible (Example: PostgreSQL 8.2)
  • Installed SCM including version if that is possible (Example: svn 1.6.11)
  • Error trace if ChiliProject crashed, if present in log/production.log
  • Publication service used (Webrick, Apache with Passenger, Thin...) if possible

That, with a template of how to properly describe a bug and a link to the tracker would probably improve bug submissions (for those which still let the administrators log in their CP of course)

Related issues

duplicated by Feature #429: User support helper script Duplicate 2011-05-27

Associated revisions

Revision 01e43f2e
Added by Eric Davis at 2011-11-25 09:50 pm

Merge pull request #134 from schmidt/pulls/725/unstable

[#725] Compatibility check for jQuery availability (unstable)


Updated by Holger Just at 2011-02-03 02:55 pm

I worked a bit on that for Redmine already. The code is at

It extends the /admin/info page and script/about output. It already shows much of the requested info. However, some of the additional stuff (like the actual database version) is really hard to get by without guessing.

I could add a How-to report a bug page with all that information pre-filled for copy and paste. Good idea here.

  • (deleted custom field) set to
  • Assignee changed from Eric Davis to Holger Just

Updated by Muntek Singh at 2011-05-27 11:59 am

My wishlist (from the redmine bug and #429):

  • Redmine Version
    • svn info
    • git show HEAD
    • Point release installed from package
  • Ruby version
  • RubyGems version
  • Rack version
  • Rake version
  • Rails version
  • Active Record version
  • Active Resource version
  • Action Mailer version
  • Active Support version
  • Application root
  • Database adapter
  • Database schema version
  • Information about the environment Redmine is installed
  • Backend server information
    • Is it running apache, nginx, passenger, thin, mongrel, etc.
      • If so what versions?
      • Where would the relevant log files for this backend typically be
    • OS info
  • Database
    • Encoding
  • Plugin List
    • Including version info of each plugin
  • Settings
    • Theme name if non-default
    • Message encoding (UTF8?)

Also available in: Atom PDF