Jonathan

I was hoping this would just be a template issue and could be added in easily and it almost can be. The base package price is available on $services[$i]['package_pricing']['price'] but this doesn't include configurable options, so it's not an accurate total renewal price. I'm not sure if coupons are taken into account here or not either. The configurable options output within their respective template are done so with this code: function packageOptions() { var pricing_id = $('#pricing_id').val(); if (pricing_id) { var params = 'service_id=<?php echo $this->Html->_($service->id);?>&' + $('[name^="configoptions"]', $('.package_options').closest('form')).serialize(); $(this).blestaRequest('GET', '<?php echo $this->Html->safe($this->base_uri . "clients/packageoptions/");?>' + pricing_id, params, function(data) { $('.package_options').html(data); }, null, {dataType: 'json'}); } } but I'm no javascript guy and this is a bit over my head to decipher into something usable to do the math to get the correct total.

+1 for transparency :)

I like your combined column approach. I'd be perfectly fine with that.

I'd like to see the renewal rate/term of a package listed on the client profile in the services table. This would make it very handy at a glance to tell which overdue invoices match a given service, etc. See screenshot.

The more I think about it the more I like this idea rather than my initial proposal.

Alternatively it could just email the reset link to them. This would probably actually be preferred. Esentially just a trigger for the forgot password email/process from the admin side. This prevents the password from ever being in plain text except when the client enters it into blesta.

A simple link in the admin interface, preferably with a confirmation popup modal to prevent accidental use that would reset the user's password, email it to them, and obviously store no copy. Customers tend to say "I forgot my password" or whatever and obviously they don't understand the "forgot password" link so an easy way to just do this for them and email it in a more "secure" way than generating, copy/pasting, and having unecessary eyes seeing it would be rather beneficial.

Looks spot on! Thanks Paul.

This sounds perfect!

It would be great if we could add addresses to CC/BCC in a ticket. If it's there, I can't for the life of me find it so someone please smack me and point it out

Kayako has a Trash Bin which is where when you click "delete" a ticket goes. From here within this folder there's an "empty trash" button. The ability to do these two things are controll be separate permissions assignable to staff/groups. This would be a pretty cool implementation for Blesta. I've attached a couple of screenshots.

We can do it with the email address - would be great if we could also do it with the from name.

We use RBL/SPF blocking but SA can also filter fased on content. I'm sure if you don't want this Blesta would implement it as a permission that could be disabled... Perhaps for regular employees they could move it to a "trash bin" but not permanently delete it. Kayako did a pretty good implentation of this we like in our main helpdesk.

Those too.

That's easy when you don't have to handle incoming spam complaints. Can't use SA much or we'd filter out legitimate complaints reaching our abuse department.

It would be great if we could delete tickets. Keeping spam tickets in the database is just pointless and skews numbers.

If you're trying to connect to the test environment then you need to add the IP yourself.

This should be a very, very, very, very very very low priority. I'm so sick of companies like Kayako, WH..., etc making a mobile app and focusing on it more than actual development of the software behind it. What's better is simply ensuring a mobile-friendly responsive layout which it has anyway. Takes far less time and development resources away from things that really matter.

This "Log Email" option as you just mentioned where it'd log the email in the same place it does the rest of the emails sent to the client (after tage replacement) is precisely what I'm after here. Not a separate log.

Discussion about implentation of this going on at http://www.blesta.com/forums/index.php?/topic/4016-mass-mail/

An option giving the ability to log or not log them would be perfect as I can honestly see times where each would be nice to have. Given only one choice I'd take the logging but options make everyone happy

Honestly I think having this log would be very important. Sure it'd "flood the log" but just adding that one email for the person would be logical as you want a complete log of emails they were sent. How else could you look at their account and see if they got a marketing email or not?

It would also be nice if you could filter based on a configurable option or addon. Very very handy actually if you needed to email only people who had X license or something similar.

How about the ability to filter out certain emails based on regexp if you perhaps didn't want to send to anyone on Hotmail, etc.? The ability to rate-limit these sending of course is a very important feature.

+1, very handy