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

I would like in the future version to glpi a ipam

The comments field is useful for our own internal project management info.

When producing POs, it is helpful to be able to make a comment that will be seen by the supplier.

These things are not that same, and the info should not be mixed, because sometimes we have confidential info in "comment" that should not be sent to the supplier.

So it would be useful to have a second field, "Comment to Supplier", next to the existing "Comment" field.

A user with a basic profile without permissions to create or validate approvals requests, he can't see any validation or approval information in the ticket. In order to see them and know the status of the validation, at least one of the four approval options must be checked in the profile.

The expected behavior is to see de request and validation approval by default in the ticket because there is no any option to setup this view.
It could be greatfull add 2 more permissions in a definition profile level:

- See or not validation requests

- see or not validation response

There does not appear to be a way on the front end to make mass / bulk changes to Knowledge Base articles. 
My goal was to create a new Target - Groups, and assign this group to a large number of Knowledge Base articles.

Seems like it can only be done in terminal or individually in the front end GUI.

Thanks!

Bonjour,

Serait il possible de gérer les ampoules /lampes de vidéoprojecteurs comme pour les cartouches pour les imprimantes.

Comment voyez vous les vidéoprojecteurs (moniteur ou périphérique) ?

Serait il possible de leur associer des consommables types lampes ?

Cordialement,

Pessoal, sobre notificações enviadas para o e-mail do requerente, preciso de ajuda. Como fazer com que o requerente/solicitante não receba notificações no e-mail dos acompanhamentos que são colocados como privado (ativando o cadeado)?

Pessoal, sobre notificações enviadas para o e-mail do requerente, preciso de ajuda.
Como fazer com que o requerente/solicitante não receba notificações no e-mail dos acompanhamentos que são colocados como privado (ativando o cadeado)?

Introduce a feature to allow users to reserve passive equipment (non-digital assets like projectors, meeting room, etc.) within GLPI, ensuring visibility into availability, preventing conflicts, and streamlining resource allocation.

I just tried the 11 beta and I saw the new tools for editing text. 
It's better than before, but being used to writing Markdown on the go, this gives me the FosWiki vibes.
- I also tried to convert Markdown to HTML but even there, code block won't follow for example.

Proxmox implemented this a couple versions ago:
Simply writing this:
## Simple markdown heading
### This is so easy and effective

- Ok now a bullet list
- Easy again

```
Code block
```
Gives this 

It could be very nice to at least toggle a markdown mode for writing then display the "View mode" in html like GLPI does.... There's a project called Perlite that perfectly fits markdown pages to a static website :https://github.com/secure-77/Perlite

Then we could make documentation flow as we link with actual cases, hardware, tickets etc, without lifting our mouse so often....

Thank you