Skip to content

KACE Systems Management Appliance (SMA)

Please tell us how you’d like to see the KACE Systems Management Appliance product improved!

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

329 results found

  1. Allow Child tickets to inherit owner across queues

    There is a check box for inheriting the owner from the parent ticket for child tickets in workflows if the child ticket is created in the same queue. Unfortunately we use multiple queues in our workflows and the ability to set the Parent Owner as the Owner of child tickets is impossible after upgrading to version 10. There is no checkbox for inheriting this field either, so we have to set the submitter of the parent to the owner we want just to assign the child to the correct owner. Not sure why they took this functionality away with the…

    24 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. Log erased tickets

    When a ticket is deleted, the action is not log in any place. There are no history and is imposible to know what is happened with it. I can't validate this system if I can't make an audit trail with its tickets.
    It would be interesting would log what, who, when and why an ticket is deleted.

    24 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Ability to hide and set a default the 'approval required before close' field...

    An end user should be able to select an approver without having to consider the 'approval required before close' or 'approval required before open' selection associated with the approver field.

    24 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Users submit tickets to only one queue but IT staff can still set them as submitters in any queue

    When a user submits a ticket, we only want them to be able to be able to choose to assign to our Service Desk queue so the Service Desk can triage and assign to the correct support queues. But we also want the user's contact info to be listed as the contact for the ticket in any queue. If we remove the ability of the user to be listed as the submitter, we can limit the queue they assign their ticket to (they only see Service Desk queue), but we cannot create a ticket in any queue on their behalf…

    24 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Sort service desk tickets by multiple columns

    not so much improve, more like bring back the old that used to work well

    I used to be alble to sort ticket by multiple columns. ie. sort first by due date, then by ticket owner (see link below)
    http://vankace/adminui/ticket_list.php?QUEUE_ID=2&ORDER[]=sort_DUE_DATE&ORDER[]=SORT_OWNER_NAME

    However this stopped working once I updated from 5.4 to 5.5

    22 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Service Desk  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. 22 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Service Desk  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Hide helpdesk Queue but allow process access

    We want to create special queues just for access via a process.
    i.e. New user creation, where we want to use the process to create the appropriate child tickets. We can do this right now, but the users SEE the queue AND the process, and they sometimes submit work orders directly to the queue instead of through the process.

    This could be easily accomplished by specifying a special "character Convention" to hide a queue (i.e. enclose in brackets, prefix with asterisk, etc.)

    21 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. Integration btw MsTeams and Service Desk, will be great if we could create a ticket directly from MsTeams Chat

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

    21 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. Pop up notification that another technician has a ticket opened

    One annoyance that we have had so far with Kace compared to our previuos Help Desk system (TrackIt) is that when a new ticket comes in, multiple people will start looking at it. Without any of them knowing someone else is working on it, you end up with 2 or more people contacting the same user about the same issue. It would be nice if there was some sort of pop up or something on the screen when you opened a ticket, that someone else already has it open. Something like "Joe smith is currently viewing this ticket". Then I…

    21 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. Service Desk - ticket alerts

    Implement some type of alerting system when a ticket owner gets assigned a ticket, in addition to the email notification. For example a separate small window that polls every 5 minutes and flashes an alert if a new ticket is found for you or for your defined custom view.

    20 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Auto assign tickets based on a "next up" rotation/round robin rotation to eqalize tickets taken

    It would work so much better for those signed into the queue to have tickets automatically assign a ticket based on a round robin type scenario or assign to those who have the least number assigned to themselves.

    It would be nice to have that as an update, click a button by the admin and it happens in our queue.

    20 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. Improve documentation of Service Desk API Reference

    I get detail information of implementation Service desk API but data is not sufficient for us.
    https://support.quest.com/download/downloads?id=6089103

    use of this documentation, I can able to login through API,
    I can Able to send query through API but I am unable to create ticket through API because in that documentation, not give proper example for creating ticket.

    Like...

    For create ticket, below is API documentation.

    POST /api/service_desk/tickets

    Description
    Creates a new ticket

    Parameters
    Body
    ticketData

    Now can you give example that how can i use this API?
    I don't know what is "ticketData"

    19 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. Read/ Write/ Hide Permissions per Queue within User Console

    I have multiple queues within my service desk; Technology, Loan Ops, Accounting. I need all users to be submitters to Technology, for purposes of email ticket creation, while having only read access to Technology within the User Console.

    However, I also need some of these users to have submitter (Write) permissions to the Loan Ops and Accounting Queues within the User Console.

    So I think there should be a way to define read/ write/ hide permission per queue within the Service Desk User Console regardless of submitter settings.

    19 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. I would like the ability to limit a user to viewing only certain queues without removing their ability to submit tickets to that queue.

    Limit user access to queues without limiting their ability to submit tickets to that queue. We have 3 queues and I do not want the user of the third queue viewing the tickets in the other 2 queues (unless it is a ticket this person submitted). Thanks.

    18 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. Kace Service Desk: Ability to enter non-integer values in custom "number" field types

    We would like for the custom field type "Number" to accept non-integer entries. Currently it will only accept whole numbers and we have a need for there to be either a way to enter decimal numbers. Please either change the current field type to accept non-integer values, or create a separate custom field type that can.

    18 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. Have values from custom fields be emailed on ticket creation.

    It's strange that you can create custom fields for the service desk but you can't have them generated in an email using the "Service Desk Email Customization".
    It would be nice if there were more 'symbols' available for the email templates. You are very limited in the criteria you can specify when emails are generated.
    Right now all that is available is
    $ticketescalationminutes, $ticketpriority, $ticketnumber, $tickettitle, $ticketurl, $tickethistory, $ticketsubmittername, $ticketsubmitteremail, $ticketownername, $ticketowneremail, $changedesc, $subject, $quoted_mail

    18 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. Add Queue Owners check boxes to the Escalation and SLA Violation email on events function

    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!

    18 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    under review  ·  Ken Galvin responded

    Thank you for contributing. This idea is under consideration and will be prioritized according to votes received.

  18. Allow User Variable in Service Desk Custom Field Query

    I'd like to query the USERFIELDVALUE table where FIELD_ID = '1' for the specific User submitting the ticket. This is just like the update query in Service Desk rules where you can specify a variable that pulls the ticket numbers from the select query, but would be for the currently logged in user (USER.ID = <USER>).

    For example:

    query: SELECT DISTINCT(FIELDVALUE) FROM USERFIELDVALUE WHERE FIELDID = '1' AND USER.ID = USERFIELDVALUE.USER_ID AND USER.ID = <USER>

    18 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. Add Location Asset to ticket fields

    For Service Desk tickets not associated with mobile assets such as laptops, it would be helpful to have a nested location field. We have multiple campuses, multiple buildings per campus and rooms per building. Having this location ability would help in triage, dispatch, and reporting.

    An example is in the forums here: http://www.appdeploy.com/messageboards/fb.asp?m=77526&key=ticket%2Clocation

    18 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. K1000 Service Desk Custom Field Addition

    When creating custom fields in Service Desk queues, it would be helpful if there was a number field to choose from that wasn't restricted to integer values. A decimal option would be ideal that could take up to at least 4 spaces to the right of a decimal (ten thousandths). Example, be able to accept 10.1875 as a valid value.

    18 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?

Feedback and Knowledge Base