This project is yet another attempt to create a friendly project management system for software development (including bugtracking) dedicated to small teams.
It doesn't include help desk / ticket system though.

In our opinion, for easy and painless planning tasks in project should be visualized as a tree - there are features, they have subfeatures, development of subfeatures can be split into smaller tasks and subtasks - to the desired level, so each separate (leaf) task would take maximum hours of work, not days or weeks.

In systems like Bugzilla or Trac (which are mostly ticket systems, by the way) this was usually done via component field (or few such fields), and you could filter by those fields.

Task tree is very convenient to see the "big picture", but when you have release iterations - one week to one month - it becomes not so easy. Then we added releases to the interface (some call them milestones or scrums), where you can put some of your tasks from the tree. If a task has some subtasks, all of them are being automatically added to this release as well. So, for example, if you add a bug to the task (as a child task) it will automatically get to the same release as the parent task.

Release is better to be presented as a plain list where you can sort by its fields or select manual sorting. Releases have progress bars where you can see its progress. All tasks are divided into 3 groups - active/done/closed. Active are tasks with statuses new/reopened. Done are fixed, verified.

You can set up your own set of statuses per project and logic of switching between statuses.
More about this:
* When task changes status, we recalculate status of its parents. For example, if task has 2 subtasks and both become fixed, parent task will also try to become fixed. If you add another subtask to it (with status new) it will try to become new (because new is more lightweight compared to fixed) but since it's usually impossible to switch from fixed to new, it will get closest possible status - which is reopened.
* When you switch task status, you can leave optional status comment (for example say that this is a duplicate, although you can create a separate status for duplicates if you like).

It is also possible to set up list of priorities, task types (feature/task/bug) and environments - all per project.

You can add release notes to the tasks. Those are things you need to do when you deploy this code to server or compile your product including this task.

Environments - when you have only one (default) you don't see it. If you add few to the project, you can use them for those:
* When adding a bug to specify where it happens and where it can be reproduced
* When marking task as fixed specify where can it be checked
* When marking release note as done you can specify where it's done (which server, which software version)

Projects also have a set of wiki pages - for project description, obviosly.

When you create a project, you need to specify its URL (which is generated automatically, but you can change it if you want).

Project can be public or private - and you can set up access permissions (owner, read/write, read-only).

You can set up notifications per project - they are sent out for adding/modifying tasks, creating release notes and other activity.

When you add a task to the tree, you stay on the same level as before. That helps for quick adding of many tasks to the same parent. If you click on the added task, you can specify its details and/or add subtasks. To specify task details just click on almost any field and it will become editable.

If you need to ask task owner about something, you can add a comment. Comments have "acknowledged" status - it allows you to track status of answers to your questions. Each conversation member can specify his own acknowledge status. If you add new comment, your ack status is being reset. You can see a list of open discussions on the dashboard.

Project dashboard is an overall view of all tasks and releases in this project. You can filter and sort them in different ways.

You also have an overall status page - for all the projects you're participating in.

Forgot to mention - this project is open source :)