I find it extremely useful to be able to hide blocks under certain circumstances. However, I would like to suggest the ability to hide blocks based on ITIL Categories. In my case, I only need to display a specific tab for certain types of tickets, and it would be fantastic if I could control which additional field blocks are shown (or hidden in this case) using a comparison operator or a regular expression.

I hope you will consider my feature request. Thank you very much.

Best regards,

When one of our technician plan a task on a ticket, its status is set to 'Assigned (Planned)' but it doesn't stop the SLA clock. So, we asked them to manually set it to 'Pending' with a 'Waiting for planned task' reason but it's sub-optimal. I think having a planned task on a ticket should pause the SLA clock directly.

In the ticketing system, when adding a follow-up to a ticket, you can choose the type of response you wish to use (Create a Task, Add a solution, add a document, ask for validation, etc.). Once you make your selection, you are 'locked' into the choice essentially and if you wish to change your type of response, especially if you have already typed out your reply, you have to copy the text, close the response, select the new response, and paste your reply.

Is there a way to make the choices interchangeable from any category without having to delete what you have you done? The way I have envisioned it is similar to internet tabs. You select the tab you want at the top of your response page and the form changes based on the selection but the textbox remains static throughout without a refresh. 

I hope this makes sense....

Summary: Streamline project code assignment by introducing a checkbox labeled "Increment in subprojects" next to the "Code" field in the project screen. When selected, subprojects created under a master project will automatically receive an incremented code (e.g., "ABCD-01," "ABCD-02"). This enhancement simplifies project code, reducing manual input and ensuring a structured and consistent code assignment across related projects.

Details:

1. Checkbox Addition:
• Introduce a checkbox labeled "Increment Code in subprojects" below the "Code" field in the project screen.
  
  
2. Functionality:
• When creating a subproject by choosing "As child of" and selecting the master project: if the master project has the "Increment in subprojects" checkbox checked, automatically fill the code of the new project with an incremented value.
  
  

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.

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.

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.  

Integrate rustdesk with glpi

Get rustdesk ID from glpi agent or add manually

Open rustdesk when click on ID URL Rustdesk 

Enable notifications queue through API request. So we can monitor how many notifications that can be error-related.

Generate ticket after change of the hardware collected by glpi agent