Unfuddle - does not pretend to Navigation and at first glance can boast nothing in comparison with other projects.
What can u offer
Select git or svn repositories; each project can have several repositories in it
Mileston'y and Ticket'y, with a standard set of features - the appointment of status, responsible, dates, components of projects and their versions. Tickets can be closed at the commit in the repository with the help of a special syntax
Local analogue of the wiki called Notebooks
Message'y that serve as a bulletin board
Overview for each project and all projects at once.
API allows you to control all functions unfuddle
Reports - Ticket samples by criteria
Time Span Reports
Management of access rights for members
And actually everything. A logical question arises, and why is this system so good? First of all, with Unfuddle, everything works as intuitively and simply as a good tool that you don’t notice in work and perceive as part of yourself. One feels that every element of the system has been thought of for a long time and productively, as a result - the minimum number of steps is required to perform any action.
Cons (where without them):
No i18n - and when it appears unknown, the authors promise, but do not hurry.
Perhaps this is IMHO, but the criteria for the division of tariffs are not the most reasonable.
Lack of ability to create Ticket status statuses and required fields
Limited wiki syntakis for Notebooks
Small summary
In my opinion Unfuddle is perfect for software developers in small and medium-sized teams in the web and other areas. We use it for several months, working on a large project managed by BaseCamp, and until that moment we tried about 10 different other systems. Neither BaseCamp nor any other project tools such enjoyment from work as Unfuddle did not deliver.