KACE Systems Management Appliance (SMA)
Please tell us how you’d like to see the KACE Systems Management Appliance product improved!
329 results found
more custom data fields in user import
We have custom reporting from the kbox database and would like more fields to be able to be imported than the stock 16. These should be listed as more custom fields.5 votes
Email All Service Desk Users or subset based on tags
Not everyone has an Exchange Server or GAL and it would be helpful if there was similar functionality built into Kbox. It would be very similar to the Alerts feature, but instead of "Deploy to All Machines" you would have the option to send to all users. Just like you can limit the broadcast to groups based on tags it would be nice to be able to limit the emails sent in the same way.1 vote
Allow custom views to be shared
Allow for custom views for tickets, assets, etc. to be shared by other users. There could be global views, team views, personal views, etc.169 votesunder review · Ken Galvin responded
Thank you for contributing. This idea is under consideration and will be prioritized according to votes received.
Service Desk: Ability to escalate tickets to additional people if still open after escalating once
We would like the ability to have additional people get added to the CC list that receives escalation emails, but only at the second and future escalations. In other words, a ticket escalates once, and a manager is notified. If enough time elapses that the ticket escalates again, we want additional people to be notified.8 votes
Hide "Also show child history" from parent ticket
I would like to be able to hide the option "Also show child history" from a parent ticket? Currently if you create a child ticket, the submitter of the parent ticket can see all of the comments of the child ticket by clicking on "Also show child history" in the parent ticket. Sometimes I do not want the submitter of the parent ticket to see the child tickets comments as it may contain information they do not need to see based on a fix or other comments from the support team. Ideally, what would happen is a user would submit a “work request” to the queue. The ticket owner would look at the request and decide what needs to be done. Instead of filling up the user’s ticket with comments, the owner would create a child ticket, which would contain all the technical details of the fix for “change control” purposes and such. This would help segregate the work request from the actual work being done and logged.
I would like to be able to hide the option "Also show child history" from a parent ticket? Currently if you create a child ticket, the submitter of the parent ticket can see all of the comments of the child ticket by clicking on "Also show child history" in the parent ticket. Sometimes I do not want the submitter of the parent ticket to see the child tickets comments as it may contain information they do not need to see based on a fix or other comments from the support team. Ideally, what would happen is a user would submit…8 votes
Branching Workflows in Service Desk
Be able to create branching workflows based off of answers made in a work flow. Example new account request may have a question do we need to order a computer, if yes create these tickets, if not then create these other tickets.56 votes
Allow admins to change the width of the label in a support ticket, not just the fields.
You can change the width of the fields that the user fills out, but the labels are held to a certain width which forces some labels to show up on two lines appearing very crowded and unprofessional.5 votes
Service Desk - Create a filter that can pull tickets from queues across mulitple orgs
A filter for admin users that can pull tickets from mulitple queues from multiple organisations. When setting up with mulitple orgs then you need to switch between them to see the tickets (can pull from multiple queues within an org) the ability for a service desk staff/supervisor to see all jobs across all orgs would be beneficial4 votes
- Don't see your idea?