Thread was closed right when it approved and posted.  Does this mean the request was denied consideration?

The feature was considered but at the end there are inevitably more issues with being able to change the owner than benefits. The correct way to send e-mails to the software is to set the owner e-mail as the e-mail sender field.

Down the road we have also planned API for various tasks including ticket creation. With the API you'll be able to easily import tickets for any user.

I guess you are going to have to ask yourself where you targeted client base will be.  If you intend on competing with Autotask and Tigerpaw, you are going to have to consider your client's requests instead of making decisions for them.

Most MSP platforms: N-Central, Kaseya, Zennith all function the same in that the "system" sends the emails to the technicians.  Therefore the email address will always be that of the "system".  I can think of a bunch of situations that you would want to change the ticket owner, like when the boss mistakenly sends a ticket from his yahoo account instead of his work account.

You have the basis for an excellent product, however some of the major issues need to be resolved, like this one and the ability to group users into defined organizations as well as some sort of customized form printing.

I hope my message is received as professional and constructive, as I like your product and want to see it succeed.

Thank you,

Matt