James Gray
My feedback
8 results found
-
51 votes
An error occurred while saving the comment James Gray
supported this idea
·
-
7 votesJames Gray
supported this idea
·
An error occurred while saving the comment James Gray
commented
I am currently able to do this via a custom Ticket Rule. However, it would be nice if this was a built-in feature because there was a database schema change that happened during one of the Kace SMA updates that broke my rule. I was able to fix it, but it would be really great if this could be a standard feature. My query uses a user label that represents a subset of users from the queue owner group. When a ticket is created that does not match any of the other auto assignment rules that are based on ticket category, it grabs the "next up" technician and assigns the ticket to that person.
-
20 votesJames Gray
supported this idea
·
-
28 votes
An error occurred while saving the comment James Gray
commented
We are starting to use Kace as an OVAL scanner and including the severity level would be very beneficial in ranking the priority for handling the vulnerabilities.
James Gray
supported this idea
·
-
11 votesJames Gray
shared this idea
·
-
40 votes
Thank you for your input. We are investigating this and encourage others to vote for this feature/functionality if they think it would be useful
James Gray
supported this idea
·
-
4 votesJames Gray
shared this idea
·
-
18 votesJames Gray
supported this idea
·
I concur. I would like to be able to track non-IT assets and give non-IT personnel access to those assets and be able to separate this by asset type. For instance, fleet assets are managed by the fleet manager, uniform and accessory assets are managed by the quartermaster. Each asset type should not be able to be managed/accessed by the other roles.