Integrate K1000 with Microsoft Teams to allow users to open tickets directly from Microsoft Teams and fill in necessary categories/information

In addition the ability to create Planner tasks for Tickets in kace would be ideal

I would like to be able to format the output when I print a ticket. I envisage it would be part of the Q configuration and it might be like the template option where you would select the fields that you want to print and some minor formatting options. Currently you get a straight dump which includes history etc and it runs to several pages of no format.

It would be nice if Kace could do something like this as so many ticketing softwares are doing this now.

When selecting Service Desk in SMA, you can see the Dashboard for whatever default queue is set up for your user profile. Some admins have access to multiple queues, specifically managers who are managing individuals in those queues, and it would be helpful to toggle back and forth between queues to get a singular view of what is happening with that queue.

There needs to be an area where I can put in an email address (Like from an HVAC, Fire System, or just a specific user, etc..) to exempt it from any replies so my customers can still get replies.

We are in the process of switching over to Microsoft Teams for our voice solution. Voicemail will still get delivered to an inbox just as it has in the past, but because there is technically no return address the SMA will not process this email as a ticket. With Teams becoming a big player in this space, a work around would be a good idea.

Current Priority settings are based on the feelings and opinions of the person submitting/owning the ticket. The ability to set a Default Priority per Category (similar to the Default Ticket Owner) in the Customize Fields and Layouts page would be very beneficial to appropriately managing workloads.

Integration btw MsTeams and Service Desk, will be great if we could create a ticket directly from MsTeams Chat

It would be awesome if all the Queue Owners were emailed when a ticket breaks SLA or Escalation timer rules.
So if you could add Queue Owners check boxes to the Escalation and SLA Violation email on events function like it has already for New ticket on ... events that would be awesome!

Process with many fases that require approval and validation on tasks.
like: Change requests - approve to begin - task1, task2, task3 - tests - (approval of results tests) move on, task implementations, next tasks ... validations task (approval of validation) ... until to end of process.

While you can show and hide fields in ticket templates with fields that are marked as required, if you go to submit a ticket and the required fields is hidden due to the logic, it will fail stating that the required field is required to submit.

Would like to see required field(s) work based on conditional logic IE, if the field(s) is marked as required but is hidden due to the conditional logic, it will allow the ticket to be submitted and vise versa.

We should be able to designate one or more persons as the manager of a queue, separate from assigning them to the "Owners" list. It is quite common for there to be a help desk manager who supervises the team, but does not handle tickets directly.

Such an assigned manager should have full visibility into dashboard statistics, receive notifications of SLA violations, be able to assign/reassign or edit tickets, etc.

If choosing to have a multiple select field in a ticket or ticket template a user needs to press CTRL-Key to select more than one item.
Please make it easier for users to select. Maybe by moving.
Another idea would be to select by single click and deselect by another single click.

Add a timer to tickets in the service desk that ticks down based on SLA. This will show techs which tickets need to be worked on next before a breach of SLA occurs.

SLA's based on time to first contact. The current SLA functionality only covers time to close. This metric is useful at times, but due to the complexity of IT issues can vary widely.

Time to first contact as an SLA is very important for all helpdesks as it tracks how long a user is waiting to be helped. This can be done with custom rules and reporting, but its cumbersome. Making it a core feature would be a big help.

We have the abilitiy to define Custom Fields as Single Select Dropdown Field.

Please implement the function (for example by a simple checkbox when configuring the field) to "remove" the first select-item "Please select one..." so that the user can only select the values which are defined for the custom field dropdown.

Right now, the only functionality based on Conditional Logic in ticket templates is whether to Show or Hide the field.

Please add the ability to set the value of the field, based on Conditional Logic. This would greatly enhance flexibility in designing ticket templates. Thank you!

LDAP Labels for (AD) users are applied to the KACE (Service Desk) User objects only when the user logged in into the User-Portal.

It is much desireable that Users are labeled with the corresponding LDAP-Labels on the time of the LDAP-Import.

Background: On a number of for example 500 Users + not every user logs into the User-Portal, therefore not every user object gets applied any LDAP-User labels.

Due to that we have no possibility to work with updated data...