Comments
-
I agree there needs to be additional setup controls on notifications so that every notification sent to Assignee doesn't automatically go to every tech in the group assigned to the ticket. Assignee and Group Assignees should be two separate notification levels.
-
In my opinion, the Printers Asset screen has some bigger issues than just lacking an asset ID number. If you look closely, it's not actually a list of printers, it is a list the printer driver names assigned on the computers that were scanned with the Discovery Agent. The same "printer" will be listed over and over again…
-
I agree with the need to fix mistakes in closed tickets, but it needs to be a separate security control/permission and any changes made after closing tickets need to be clearly logged in the Audit trail.
-
Just my opinion, but fields are fields, whether built-in or custom, All fields should be available for notifications, filtering, sorting, reporting......it's a database platform it shouldn't make a difference which type of fields are available for which screens or functions.
-
Portal Announcements should stand out and be front & center (attention getting). Font Colors, Background colors, Font Sizes, inserting images - every feature that's available in portal text message box should be available for portal announcements.
-
Sounds like this is a software bug which needs to pushed over to support and fixed. Hard to believe it's been sitting here in feature requests almost 5 years!
-
This is a must have as far as I am concerned. There is no logical reason for Assignee notifications to automatically include group assignee. I'm really surprised that this group assignee feature wasn't rolled out as beta-test function in Labs before being pushed to live production, so the users had a chance to test and…
-
Yes, many are blank, and many are very dated or just plain wrong - it could be a very powerful reporting tool/filter if we were allowed to manage it
