Is it possible get or associate the PC that send the ticket to the ticket?

Thank you.

The URL at today is: http://myurl.com/front/funtionality.php?id=XXX or http://myurl.com/plugin/funtionality.php the idea it's change this trough htaccess for http://myrul.com/funtionality/ID I mean the URL change to this: Example the URL for projects it is:http://myurl.com/plugins/projet/front/projet.php the htaccess change just for /project/ and when you chooose a project appear form this must be changed too so: form + ID it's reduced so the final it's http://myurl.com/projet/01 or ticket case Example the ticket URL it's: http://myurl.com/front/ticket.form.php?id=000000 the htaccess change just for /ticket/ and when you chooose a ticket appear form this must be changed too so: form + ID it's reduced so the final it's http://myurl.com/Ticket/20153001

When you try to close a ticket and you missed to fill a mandatory field (eg category), the response field you took time to fill is TOTALLY EMPTY after clicking on save...

I would like in the future version to glpi a ipam

We use the plugin and it works very well for us, but we are missing some functionalities. Could you consider including them in future versions?

• Improvements for the filter: make it search in the titles of projects, tasks, and subtasks.
• Export format: try to add some format like PDF or Excel for printing.
• Add the option to Show/Hide linked tickets in subtasks and make them clickable. The idea is that it should be optional. They should only be displayed if "Show" is selected.
• Add the possibility to add tickets directly, just like it currently allows adding new subtasks. Provide the option to add tickets in subtasks and have them linked to the project and the project task.

I'm using GLPI 11.0.4 as a Docker container.

In planning view I was not able to use the full available window height.

The only method I found was to manually edit line 93 of file planning.js inside the container, from 

height: options.height,

to

height: '100%',

and fully refresh the page in browser.

This value seems to have a default value set at line 55

height: GLPIPlanning.getHeight,

This behaviour is a bit annoying because I have to reproduce this modification at every containter recreation.

It should be nice if that value was parameterized somehow as many other parameters are already.

I’m trying to implement sequential approvals on Enterprise Service Management forms/tickets. I attempted to use Business Rules, but as soon as I add an additional criterion—such as Description → Contains, alongside Approval → Granted—the rule fails to trigger.

My requirement is to have different approvers for different types of service requests (e.g., recruitment requests, termination requests, leave requests). At any stage, if an approval is refused, the approval flow should stop and the ticket should close.

The challenge is that I cannot add additional criteria in the Business Rule to differentiate request types; as a result, the rule would apply globally to all tickets where approval is granted, forcing me to configure only one user or one group as the second-level approver—which defeats the purpose. ESM forms require different approvers depending on the request type.

Has anyone managed to solve this using Business Rules?

My other option is to explore configuring Entities, which in theory should work—but so should the rules, at least on paper. :(

Bonjour l'équipe et la communauté,

Je souhaite proposer une amélioration concernant l'interface utilisateur de GLPI 11, spécifiquement au niveau du menu Parc (Assets).

Le constat : Actuellement, tous les types d'équipements (Ordinateurs, Moniteurs, Réseau, Imprimantes, Périphériques, etc.) sont listés au même niveau sous le menu "Parc". Avec l'ajout d'objets personnalisés, cette liste devient très longue et difficile à scanner visuellement.

La proposition : Serait-il possible d'introduire une fonctionnalité (native ou via configuration UI) permettant de créer des sous-groupes visuels ou des séparateurs dans ce menu ?

L'idée n'est pas de changer la structure de la base de données, mais uniquement l'organisation visuelle du menu.

Exemple d'organisation :

Parc

--- Infrastructure --- (Séparateur ou Sous-menu)

 Réseau

Rack

PDU

--- Postes de travail ---

Ordinateurs

Moniteurs

--- Périphériques ---

Imprimantes

Téléphones

Cela améliorerait grandement la navigation au quotidien pour les techniciens. Qu'en pensez-vous ?

Merci pour votre excellent travail sur la v11 !