AdminKen Galvin
(Product Owner, Quest KACE)
My feedback
-
144 votes
This is under consideration but not planned for the next release. Please continue voting if you’d like to see this feature prioritized for a future release.
An error occurred while saving the comment -
96 votes
This is under consideration but not planned for the next release. Please continue voting if you’d like to see this feature prioritized for a future release.
An error occurred while saving the comment Can you tell us what Response Templates do not allow you to do.
-
16 votes
An error occurred while saving the comment We do not auto-filter per se; but we do have a View By Family which we believe accomplishes the same thing. We will keep it under review so that more people can vote if they want this.
-
15 votes
An error occurred while saving the comment We do not support this and it is not planned at this time. However, as a possible workaround, let the user create a ticket on the queue to which he/she has access, then the admin will move that ticket to a queue to which the user does not have access. By doing this, the user can still see his/her ticket but will not see any other ticket on that new queue. We hope that helps.
-
357 votes
Location was done in 10.1 and we are reviewing ways to add additional fields.
An error occurred while saving the comment We would appreciate input on what specific fields you would be interested in. Thank you in advance for your suggestions.
-
6 votes
An error occurred while saving the comment Just so I am clear, let me know if this scenario captures your request. There is a ticket rule that can be enabled that will automatically reopen a ticket should the enduser reply to a closed ticket email notification with something like “Hey don’t close this out, I’m still not fixed.” The ticket rule engages and then automatically changes the ticket to “reopened”.
But let’s say that enduser said “thank you, great job” – technically we will still reopen the ticket since the rule is doing exactly what is expected. The customer wants the enduser to be able to close it out at that point and we will not allow the enduser to do so. Only the ticket owner can close it out. That is working as designed.
If this is the case, the best option would be to just turn that rule off and not use it. You can make the Status field an “editable” field and the enduser can close this ticket out from the portal if they need to or reopen if they need to. Will that help - even temporarily? I ask because there are so many higher rated requests, that I am not confident that we can move this into a relase anytime soon.
-
76 votes
An error occurred while saving the comment This was delayed but is still planned. Our apologies for the delay.
-
251 votes
An error occurred while saving the comment -The implementation level certification courses are available to customers, partners, and employees.
-Currently, the implementation level certification tests are available to partners and employees and not customers.
To learn more about the free courses available to customers, please check this out:
https://www.itninja.com/blog/view/free-training-on-kace-productsWe will leave this request open for future consideration.
Please try the following and let us know if this does not satisfy your request:
If you want ALL users to access and update ANY ticket field on a certain queue, then we must make ALL users as owner to that queue.
If you want to keep the queue owners restricted, then CC List would be your next bet. CC List users CAN add comments and attachments to the ticket.