It would be usefull to add in profile, an option allowing ticket creation from another entity.

When a notification contains multiple recipients, GLPI sends one mail per recipient.

Is it possible to change this behavior to send an unique mail with headers ?

For example, when recipients are requester and watcher. GLPI should send an unique mail with following headers :

- To : requester(s)'s e-mail address(es)

- Cc : watcher(s)'s e-amil address(es)

WebRTC is a new open framework for the web that enables Real Time Communications in the browser. Moreover it enables the voice calling, video chat, and P2P file sharing without plugins for browser-to-browser applications. WebRTC offers web application developers the ability to write realtime multimedia applications like video chat on the web, without requiring plugins, downloads or installs. It's purpose is to help build a strong RTC platform that works across multiple web browsers and multiple platforms. The major component of the WebRTC are: getUserMedia, PeerConnection, DataChannels. The first allows a web browser to access the camera and microphone. The second sets up audio/video calls. The last one allows browsers to share data via peer-to-peer. Do you imagine this in GLPI? It's JUST AWESOME!

Add more possiblity to manage contratcs :

- add users/groups in charge of contratcs

- send notifications to the groups/users in charge

- auto-create tickets when contratcs expired, Ticket assigned to groups/users in charge

When I enter the Setup - Components menu and select some type of component (e.q. Processors), I would like to be able to add Number of Items in the columns settings.

Rationale: to know, how many of each model of component we have.

We would like to suggest one option to activate the possibility to only close the ticket after 100% of the approvals, in case with more than one users responsible for the approvals.

Hey folks.

Currently, the only way to restrict if an ITIL dropdown is being shown while creating a ticket, is to make use of a sub-entity.

This is rather suboptimal solution (its suboptimal for almost anything to depend on different sub/entity).

We do not wish to have the default users being able to see/choose ALL of the ITIL dropdowns, since some of them are supposed to be internal to the teams using them. But those teams may also have ITIL dropdowns that MUST be visible to anyone. If they create an entry, it will be visible only for them (since its in their sub-entity).

Which makes it absolutely terrible to manage them.

Hello currently I would like to receive an email notification on GLPI with the number of tickets that is open and the number of tickets closed on each month of the year. Having no knowledge of this subject

It would be nice to have the Assigned To field be splitted in Assigned Group and Assigned Technician. I believe it has long been like this and it would be it as an option and/or improvement.

About the e-mail functionality, in my system the Requester and Observer receives the Answers update individually, this confuses them that they are the only one receiving the update from the technician. Wouldn't it be nice to have a one e-mail thread that already includes both requester (To) and observers (CC)?

Lastly, can the ID of ticket type Request and Incident be different? It is just plain numbers and having a naming convention would just be nice. (i.e. INC-#######, I-#######, SR-#######, R-########, etc.)