By Quenten Grasso
It would be great if we had some integration with https://chocolatey.org for windows package management, its basically like apt-get or yum for windows which seems a lot better IMHO then ninite type solutions.
Having its own tab under group policy for example to install selected apps across multiple machines and keep them updated within patch windows for example. This would be a huge benefit for Pulseway if done well.
https://chocolatey.org/pricing at only $3/year per machine its pretty competitive pricing.
By Quenten Grasso
I'd like to submit a feature request to be able to disable items which are not being used such as NOC, Setup, Slack Integrations, Backup Plugin for example. maybe under server admin -> settings -> option under here for example?
By Matt Wilson
I am aware that I can add an invoice-wide discount, but we really need a way to invoice line items. The only work around is to generate multiple invoices when you don't want the discount to apply to entire invoice. I want customer's to see the actual normal price, I don't just want to edit the extended price.
Also, I like the new billing automation feature. But we also need to a way to add a (hopefully future line item) discount to the billing automation. We generally offer a discount on recurring flat fee services for the first 6 or 12 months of the term, and I need a way to put this in so that I don't have to manually change everything on each invoice after it is generated and/or exported to QB like I do now. Manual invoicing is such a time waster.
As always, Thanks so much!!
By Matt Wilson
I had a big issue today where replies from clients were not adding the reply as a note, but instead creating a new ticket altogether. In the end, there were 2 causes.
1) In the default PSA email templates, the Ticket number was set as #Ticket No#. This looks really weird in my opinion, when referring to a ticket number its generally "Ticket Number" or "#Ticket Number". I had removed the trailing # on most of the templates. I searched the knowledge base and forums and there was no mention, so it was only through trial and error that I realized that you HAVE to have both # at front and end of ticket number for replies to work.
2) In some templates, I removed the Ticket number all together as it really had no purpose. I would much rather use a Subject line like: "A note has been added to your ticket regarding [%Ticket Title%]" Again, through trial and error I realized for replies to work the ticket number (formatted per 1 above) must be included in the subject. There was another forum post from someone having issues with replies on CC's. In that thread they thought the same thing I did, that adding the Reply Separator field in the message body had all the needed coding to enable replies to the ticket.
I am posting this for anyone else who may be searching for this and to also request that header info be embedded in the Reply Separator field so that it is all that is needed to enable replies as notes back to the originating ticket. Also, some documentation on this feature and associated troubleshooting may be a good knowledge base article to post.