Jon DeMersseman
My feedback
18 results found
-
76 votes
This is under consideration but not planned for the next release, Please continue voting if you’d like to see this feature prioritized for a future release.
Jon DeMersseman supported this idea ·
-
83 votes
Jon DeMersseman supported this idea ·
-
15 votes
An error occurred while saving the comment Jon DeMersseman supported this idea ·
-
764 votes
An error occurred while saving the comment Jon DeMersseman commented
Seems like this is going nowhere, but honestly this is a completely different software category.
-
19 votes
An error occurred while saving the comment Jon DeMersseman commented
There is an archive user feature in KACE. Purging users may have unintended consequences on related records.
-
16 votes
An error occurred while saving the comment Jon DeMersseman commented
This is an interesting idea, but explain how this would be different than what is available via LDAP. As I understand you, you want to use OU's for scheduling, but LDAP would definitely identify the OU.
-
7 votes
Jon DeMersseman supported this idea ·
An error occurred while saving the comment Jon DeMersseman commented
It would be great of their was support for multiline code (we use QR) locations as well. We have multiple sites and multiple suites within a build so our locations are Cube / Office, Suite, City.
-
77 votes
Jon DeMersseman supported this idea ·
-
123 votes
We’re looking at this after we get more K1000 synchronization built into the K2000.
Jon DeMersseman supported this idea ·
-
13 votes
Jon DeMersseman supported this idea ·
Jon DeMersseman shared this idea ·
-
71 votes
Jon DeMersseman supported this idea ·
-
443 votes
This feature request is under review. We encourage others to vote for it to be considered in a future release.
Jon DeMersseman supported this idea ·
-
275 votes
Jon DeMersseman supported this idea ·
-
160 votes
Jon DeMersseman supported this idea ·
-
272 votes
Jon DeMersseman supported this idea ·
-
34 votes
Jon DeMersseman supported this idea ·
-
45 votes
Jon DeMersseman supported this idea ·
An error occurred while saving the comment Jon DeMersseman commented
This feature could be incredibly powerful and eliminate the need for SMS paging.
It could be strengthened by adding other Incident management features, like an on-call schedule for each tier so only the technicians and engineers on call are notified. This could be paired with escalation features so if the first technician doesn't respond the next is alerted, etc. -
9 votes
Jon DeMersseman supported this idea ·
Jon DeMersseman shared this idea ·
This is pretty a standard part of many user interfaces. Please implement this in v. 11.