I would like to be able to work on issues (a local repository copy) when there is no internet connection, and sync my local work back up to the "server" when there is an internet connection. This makes the client more of a peer than a client/slave.
The problem this solves is being able to keep working with WI when there is no network connection, the network connection is bad, or the network connection is untrusted. Examples; On an airplane, at a conference, when the connection is saturated with someone's torrent activity (college dorm), or the network connection is very expensive.
Think along the lines of how GIT does version control. There is a local repository on the local disk where work is kept, all GIT features are supported, and a server (or two or three) where work is pushed (or Sync'ed) at convenient times.
When I saw WI had a client, I was desperately hoping this kind of feature would differentiate WI from the rest of the pack. I discovered the WI Windows Client is heavily dependent on a connection to the "Server" and won't work without this connection. i.e. I don't see much value over just using the Web interface, like every other bug tracking system in existence today. I installed WI, like what I see, and wish it could do more.
Hopefully the installation of such a Standalone client will will be as lightweight and easy as installing GIT. i.e. I'd rather not clone my server on my laptop with Apache/IIS, MySQL, etc.
I hope you'll consider my request.