We ended up just making our own inbound email parser :(

Updated the title to hopefully attract some more voters. We've had to tell two of our clients in the last week to login with emails of something like theirEmail+leveldata@theirdomain.com instead of just using their email address because of this... The solution that helpdesk gives is to capitalize on...

We just hit this in a real world scenario, and I expect this to keep happening to us periodically. We have to change the users username to email+leveldata@leveldata.com :(. The explanation to our client is "Sorry workfront (the project management system we chose to make this work easier than email) ...

Inbound email -> Formatted text I'd hope is a part of this but just in case! If you guys do touch the inbound mail parser maybe also deal with attachments, and inline images.

It'd be awesome if that integration included comments (notes) as well.

Every tool I use to interact with workfront has this (Email, Zendesk, Idea Exchange, Community Forums), but workfronts own tool doesn't :(

+1 a lot of our users are using the Commit Date for this type of thing (Not correct, but it has worked for them and our project managers). They respond to a task/issue and then push the commit date out to the date they are committing to "do something" on the issue not necessarily complete the issue/...

Heather's solution is better, a combination of that with maybe an alert in the browser or something to indicate that your response isn't going to be sent to anyone would be great! My view point is that it's better for us to have no comment than to have a comment go to nobody as our customer will hav...

I think this was touched briefly in a few of the other comments, here's a bit more information about sorting:We'd like to be able to change the order at which the fields are listed in the chart. It'd be great if you could sort by any field that you wanted, our specific use case is MileStone names, w...

Yes, audit trails across the entire application would be awesome as well. It can be really hard to know how something got into a state that it did without knowing who set the status of this project / task / issue to what when.