Rob Seamon
My feedback
-
15 votesRob Seamon
supported this idea
·
-
1 voteRob Seamon
shared this idea
·
-
162 votes
An error occurred while saving the comment -
188 votesRob Seamon
supported this idea
·
-
250 votes
Thank you for posting this request. We encourage others to “vote it up” for consideration in a future release.
Note that as of SMA 8.0, you can manually archive users, but the understanding on this request is that we automate it and that is what is under review.Rob Seamon
supported this idea
·
-
905 votesunder review · 16 comments · SMA (K1000) » Software Compliance · Flag idea as inappropriate… · Admin →Rob Seamon
supported this idea
·
-
8 votes
An error occurred while saving the comment Rob Seamon
commented
It is set this way now and has been for a couple of KACE versions at least.
-
7 votes
An error occurred while saving the comment Rob Seamon
commented
It would be nice to use the GUI to do this rather than making a rule that say if category = this or this or this then set owner to [username]. It could be easier to change via the GUI instead of the rule if an organization needs to change their default owner quite often.
Rob Seamon
supported this idea
·
-
14 votes
Thank you for contributing. This idea is under consideration and will be prioritized according to votes received.
An error occurred while saving the comment Rob Seamon
commented
You can hide the priority field from submitters leaving only the Owners to choose what the ticket priority ends up being in the end. Training potential ticket owners on the proper use of the field would greatly minimize the need to add this function at all.
-
1 vote
An error occurred while saving the comment Rob Seamon
commented
I see what you are asking for but they may not be able to make a user label "fit into" a data field designed for a single user.
As an alternative would adding the Distribution list (or comma separated emails) into the category CC field and checking the boxes for category cc on new ticket via email and new ticket via portal do what you want in relation to notifying the whole owners group that a new ticket is in? -
51 votes
An error occurred while saving the comment Rob Seamon
commented
We know someone who would like to be able to limit visibility of Assets to particular Owner labels or Roles.
So that an "A" owner cannot see or edit a "B" asset inside the same Org.
It maybe could be done by adding an Asset Scope section (like the current Device Scope section) to the Role page.
Or it could be done by treating Assets like Knowledge Base articles and having the ability to set a "visibility label" per Asset.Rob Seamon
supported this idea
·
-
160 votes
An error occurred while saving the comment Rob Seamon
commented
Please add
Rob Seamon
supported this idea
·
-
23 votesRob Seamon
supported this idea
·
-
4 votesRob Seamon
shared this idea
·
-
17 votes
Thank you for contributing. This idea is under consideration and will be prioritized according to votes received.
Rob Seamon
shared this idea
·
-
10 votesRob Seamon
supported this idea
·
If the "Automatically Reboot When no one is logged in" problem with the system account being counted as a logged in user has been fixed in newer versions can this be closed out now?
Otherwise the admin would have to set the timeouts and tries to small enough numbers so that if just a system user is logged in overnight that it will be rebooted by morning.