Hello. FYI, Redmine is a rewrite in Ruby of Trac (programmed in Python), with several improvements. Later, some developers from Redmine made a fork of it named ChiliProject, to go more faster in development. I recommend ChiliProject over Redmine. ChiliProject have all characteristics that you list, plus LDAP and OpenID authentication, much more.
https://www.chiliproject.org/ https://www.chiliproject.org/projects/chiliproject/wiki/REST_API But... I have a look a fogbugz.com :) El viernes, 8 de febrero de 2013, Camillo Bruni escribió: > With the recent announcement of google code to shut down their public API > I see > a major functionality gone for our project. > > https://code.google.com/p/support/wiki/IssueTrackerAPI > > I would like to extend the functionality of our monkey, so it will become > more intelligent: > - give code critics feedback > - reject new code that doesn't meet our criteria in general (unclassified > methods / uncommented classes) > - failing tests are serialized and attached to the issue > - image with the changes integrated are attached to the issue > > ... you get the picture. All this stuff is impossible to achieve if there > is no scriptable > API available. By dropping that, google code becomes a silly toy with no > further use to me. > > > Requirements > ------------ > So, we have to come up with a new issue tracker by june with the following > requirements: > > - dead simple issue reporting (most of the stuff out there just looks like > a control panel for a space ship) > - scriptable API > - file attachements > > Additionally: > - programmed in ruby or python > - easily create sub-projects > ...? > > Issue Tracker > ------------- > - I like trac a lot, but no API from what I read > http://trac.edgewall.org/ > - Jira, thats the space-ship-panel (and in this very same category, > buzilla...) > http://www.atlassian.com/software/jira > - github? too simplistic no file upload > https://github.com/dalehenrich/filetree/issues > - redmine, possible kandidate > http://www.redmine.org/ > > > So what is your take on this? >
