It would be great to be able to relate issues is few ways:

* As a dependent (like milestones), sub-issue block the closing status of the parent issue.
* As related somehow
* As a duplicate

It would be very nice if we had the option to export all of our data. Either for the whole account or per project.

Would be a shame to commit to using a service like this, and need to move away for whatever reason... and loose all the information that's been collected through the tickets / wiki pages.

It would also mean we could take our own backups of the information.

CSV files or something would do, then its up-to us to extract the data we need.

We like to account for our time depending on the phase or area of the project on which we're working. Since Codebase already has handy milestones built in, it would be great to be able to track time against a milestone, rather than just a project, and then get per-milestone reporting (in addition to the per-user and per-project reporting that is in now).

I think the project planing ability of codebase is not flexible and not agile enough. I would really like to see something like: http://kanbantool.com build into codebase.

They are in early beta, so maybe you can do some kind of cooperation with them.

I know this is a real big thing, but this would make codebase absolutely unique and I would really be happy to pay twice as much and having an all-in-one solution.

have a diff view that shows two revisions of the code in side by side comparison mode.

Hae a function to allow the tickets by project to be exported to Excel or CSV file

The one redeeming quality of BaseCamp was the ability to use a 3rd party to generate invoices from time-tracking data.

What about an app client for codebase users? would be great to check the projects on the go

There is a changeset count on each user's profile page. Many of my commits were done with a "username@MachineName" email address, that isn't accepted as a valid email address by the system, hence they aren't counted. Could you please change your model, so that you can add invalid email addresses (but if you want, not allow them to be selected as the default email address.) Please.

Give the ability to adjust the ticket order within a milestone. Then it would be easier to plan a milestone in advance. Often there are dependencies to other tasks that need to be completed first. Alternatively there could be a ticket dependency in a ticket.

See www.coffeescript.com

It's key to have visibility on how our developers are spending their time. i.e if you pay $/h

Often, a feature idea or a bug is discovered while using my Codebase-hosted iPhone app that I'm currently developing. It would be great if Codebase would make an iPhone-friendly CSS for the website so I can log my feature requests, bug tickets, etc.

Would be great to see the codebase in russian.

Since the names of tickets don't always make sense when outside the context of its milestone, showing the related milestone (perhaps below) would be very helpful.