Please check if the feature has not already been requested.
If not, please describe it
Integrate GLPI with BeyondTrust Remote Support
BeyondTrust Remote Support is an HelpDesk tool, to connect to remote machines securely.
16.000 installations in the world, some of the customers use also GLPI.
It could be a good option to connect directly from a ticket to the machine.
An extended API exists in Remote Support to start this connection.
Public current search by entity and group
Possibility of sharing pre-designed Filters/Markers between users
Good morning, the possibility of being able to share among selected nominative users the different filters/Bookmarks that are created as predefined queries is suggested. Currently, they must be made public to all personnel who use GLPI or private. It would be useful to be able to share it among selected users of the same team, etc. so you don't have to create the same query for different logins in a custom way.
Thanks in advance.
Ability to deactivate the stripping of quotes for follow ups etc.(and with that deactivating the delimter lines)
In the real world it is simply impossible to teach all staff and costumers to always remove automaticially addded information above the delimter line (i.e. Outlook's automaticially added "From, Sent, To, Topic"-Lines, the so called Outlook-Header).
If such auto-added information is not manually removed prior sending the mail to glpi, the tickets will look very confusing and further notifications mails will become litterally unreadabble due to all the content segmentation in the mail-body. This renders the Ticketsystem unusuable in some use cases (i.e. wehere mail is the most choosen way for ticket-creation and follow ups).
Therfore we have demand to simply deactivate this content-stripping on incoming mails and with that the insertion of delimter-lines in the outgoing mails. In the best case there will be an button to activate/deactivate content-stripping and delimter lines.
It is cllear, that the tickets can have multiple qoutes multiple times then, but after all, the ticket and notification-mails will stay redable and understandable. This kind of behavior is used by other systems like OTRS and is of course widley accepted by admins and users.
Enable notifications queue through API request.
Enable notifications queue through API request. So we can monitor how many notifications that can be error-related.
open ticket after hardware change
Generate ticket after change of the hardware collected by glpi agent
Domain & Domain Record management - be able to associate a knowledge base entry & Certificates & Associated items
We diligently use your excellent certificate tracking tool and the knowledge base tool.
As part of the management of renewal and follow-up of certificates, we have procedures to help with renewal. For this, we use an entry from the knowledge base.
Unfortunately, when managing domains, we cannot associate a knowledge base entry to it.
When managing domain records, we cannot associate certificates, knowledge bases or associated items to it.
Would it be possible to activate these modules on the pages concerned?
(Here is a request that might look like this request. ticket )
Best regards
source ticket:https://github.com/glpi-project/glpi/issues/14891
Incidents based on changes (or other objects) - specify cause of ticket
We've seen that we can associate tickets and other types to a ticket. But how to distinguish e.g., between a change that was a result of a ticket and a ticket because of a change?
One can associate changes in tickets but there is no indication if the change was the result or the (root) cause of the ticket.
Wouldn't it be a useful idea, to specify the cause of a ticket? And causes could be changes (most likely), or other objects like project tasks, release, etc.
Also, in the solution-entry one can specify a solution type but no relation to a type (e.g. a change).
Wouldn't it be a useful idea, to specify the solution of a ticket and link the "solving" item (e.g. a change)?
XML export for assets
Hello, it will be very helpfull to have a export to XML of the assets. This can provide to export asset to a monitoring application (for example Zabbix). Thank
Create a ticket from Ticket
Hi,
it will be useful with Incidents and Requests:
1) Manually create a son ticket from a ticket. With different Category, like sub-ticket in form of predefined ticket template
2) Business rules for tickets when, as example, we choose a special category, or a new one action element and create several tickets automatically. Like a process management
For a simple example, HR creates a request for a new employee.
We use some action element or choose a special ticket category. Automatically system creates several new tickets:
1) A new ticket to division who is responsible for ActiveDirectory services and creates accounts
2) A new ticket to telephony and networking division to provide LAN access and phone
3) A new ticket to division who responsible for workstations etc
Mechanism like Projects in GLPI, but based on tickets, this is just hiring. Anyway protects don’t have business rules also
Package Deploy - In audit compare against lower or higher version of the exe file (or add software criteria to dynamic groups)
Very often you have to check if an application is already installed and at the same time if the version of that application is lower than the one is going to be deployed.
If audit can compare against version of the .exe file we can install only if the version already installed is lower then a specific version.
Another solution could be add criteria in dinamyc groups based on specific software installed.
Сервис поддержки клиентов работает на платформе UserEcho