Skip to content

Stephen Delinski

← Customer Feedback for Quest KACE

My feedback

2 results found

  1. Additional filter options with Organizations

    20 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    2 comments  ·  KACE Systems Management Appliance (SMA) » Organizations  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    An error occurred while saving the comment
    Stephen Delinski commented  · 

    With the filters currently available, There is no way to proactively label/filter devices by useful metrics. OS_Version, TimeZone, Domain, Etc all should be available as filter criteria.

    At the moment, our only option is to manually reassign devices by hand, rather than any system logic.

    Stephen Delinski supported this idea  · 

  2. Help Desk - Allow non admin user to duplicate a closed ticket

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  KACE Systems Management Appliance (SMA) » 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)
    Close
    Close
    An error occurred while saving the comment
    Stephen Delinski commented  · 

    I have been back and forth with Support about a similar issue.

    In our environment, when a user tries to duplicate a closed ticket, the location field (Required) would not populate, making the user unable to submit the new ticket form.

    Custom_1 field | single select text | always require | user modify

    There are two observed issues here;
    Issue 1)
    Regardless of the user’s permission to the field, the custom_1 field should still populate with the info from the original (duplicating) ticket. This is not happening.
    Issue 2)
    If on Original ticket submission, user modify permissions allow a user to initially set the custom_1 field, then on ticket edit, they can modify.
    On Duplicate, the modify permission does NOT allow the user to create the field, which is why is does not populate.
    Although these two issues seem like obvious issues, the upper tier specialist/developer on the ticket (not the front line support person) stated that this is intended functionality and not considered a bug.

Feedback and Knowledge Base

(thinking…)