Please check if the feature has not already been requested.
If not, please describe it
Had to be added as a business rule for tickets action, where you could select the group where tickets with no tech assigned would be distributed.
Of course, it would be great to have a Load Balance auto-assignment system. It would be harder to code, though.
The datacenter / rack view of 9.3 is really great, but I would suggest some enhancements regarding the power and PDU management:
For what I experience, the relation is as following:
Wall Power Outlet(s) <---> PDU Inlet(s) | PDU Outlet(s) <---> PSU Inlets (Power Supply Inlet(s) of Computers/Monitors/Network Devices, etc.
Currently there seems to be no connection between the Rack PDUs and Equipment PSU possible.
So here my ideas:
Create types Inlets and Outles, add them to PDU/PSU types and make connections between them possible: this should be roughly equivalent to the network 'Ethernet port' type.
And some minor other issues with the current implementation:
1) Plug = Outlet? And what does the 'Number' characteristic of a PDU plug mean?
2) It is not possible to add external links to PDUs
Enable Single Sign On, OAuth 2, SAML, Open ID, Social Login with:
For admins and users
LDAP and Active DirectoryConnect to existing user directories
Social LoginEasily enable social login
Identity BrokeringOpenID Connect or SAML 2.0 IdPs
High PerformanceLightweight, fast and scalable
Password PoliciesCustomize password policies
Signature verification and PDF sign example:
A general-purpose, web standards-based platform for parsing and rendering PDFs.
We have implemented both signing and signature verification of PDFs in browser using https://pkijs, you can see an early signature verification demo here: https://pkijs.org/examples/PDFexample.html we have not yet integrated with PDFjs but will be doing that in the not so distant future. Our intention is to release most of this as OSS and give back any changes to PDFjs that are necessary to make integration smooth.
I appreciate it very much if there are more users fields of options to synchronize with the existing information in Active Directory in "Setup->Authentication->LDAP Directorys->MY AD CONFIGURATION>Users", combined with Administrations-> Users.
In "Administrations->Users->MY USER FROM AD->User", there is the "LOCATION" field, but in "Setup->Authentication->LDAP Directorys->MY AD CONFIGURATION->Users", there is no field with this option so I can sync from AD this information.
Thus, other options that would be important to sync with AD:
Name in AD
Can you please make a feature to allow documents to be made private in a ticket.
Every now and again we need to attach a documents to a ticket that contains private information.
As documents are not private we have been saving these documents into our departments shared network drive.
Not saving these documents to the ticket often causes issues if the case is reviewed at a later date.
Let's say someone creates a ticket in our system. We may need to be contact 3th parties for the ticket. We perhaps would contact someone else (his boss, a supplier) through mail. In GLPI you have to do that through other means, and log the result in GLPI once done.
The problem with this is that it's much harder to have teams working on a ticket, as some info is handled outside the ticket.
GLPI could allow the agent to pick a user to send a mail to. (This mail could be marked as private even by adding something to the mail, that way a reply would be private too).
This is something that is handled for example in OTRS in a very good way.
Customer support service by UserEcho