It would be great and would look more professional if I could have access to assembla and all the tools from my own domain, such as

assembla.mysite.com

or for particular space

assembla.mysite.com/space.

Right now its assembla.com/spaces/space.

It would be much better if clients would have the impression the tool is on our site.

Add codeblocks with syntax highligtning for the wiki part of the space.

To show costumers / coworkers how to use the latest addition or when discussing /planning certain pices of code.

ref somthing like this
http://code.google.com/p/syntaxhighlighter/

Add the ability to make ticket relationships across spaces under the same subscription

it should let you view your projects, create a new ticket, see the tickets, assign tickets, comment on tickets, or change a ticket's status.

Ability to create and manage tickets via the new netbeans issue tracking plugin.

integration of gantt functionality would be great, even stand alone at the beginning would be of great benefit

- select space & ticket, press START/STOP to count time for this ticket
- aplication is always present in system tray, logging to assembla is not needed for every ticket
- change status of ticket from the application
- link to the ticket in assembla

It will be easier to accept new users with russian

We have a project that requires at least a half a dozen git repositories for the various components of the project. I like the new feature that a project can have multiple repositories. Is there any plan to allow us to name the repositories a little more cleanly?

Right now the following happens:
git@git.assembla.com:myproject.git
git@git.assembla.com:myproject.2.git
git@git.assembla.com:myproject.3.git
git@git.assembla.com:myproject.4.git

This is a little messy. The numbers don’t mean anything to us. It would be much more useful if these were named:
git@git.assembla.com:myproject.git
git@git.assembla.com:myproject.some-component.git
git@git.assembla.com:myproject.web-services.git
git@git.assembla.com:myproject.class-library.git

It would be very nice to have as an owner possibility of connecting team member with his $/per hour price. Paychecks would be easy as one two three. Additional feature would be setting price in a period of time for ex. Martin 01.10 - 02.12 10$/h, Martin 03.12.08 - 05.01.09 15$/h (because it's christmas time). I would be very easy to control bonus hours, in one listing.

For printing or offline review

Allow to define "Access Levels" on each content instance (ticket, wiki page, milestone, etc.) created in a space, then allow to group space users and assign none/read/write/delete privileges to each group for each access level. This should be an optional additional granularity to current module level access privileges setting.

Agile Planner is nice, but only Sprint Backlog has the burndown chart. There needs to be similar thing for release planning and product backlog burndown and team velocity.

Currently you can import tickets from Trac into Assembla's integrated ticketing system. It would be very useful if the reverse operation was possible too (from Assembla to Trac).

example pre-commit hook usage:
- force people to provide a commit message
- check that filenames are case-insensitively unique
- check that each file has proper MIME type

example post-commit hook usage:
- send commit stats to CIA.vc !
- send commit notification email

If you're using the wiki for a project design doc then it would be very nice to have a simple way of exporting to a single document you can store. The pages can simply be arranged in order.