Welcome to GLPi feature request service.
Please check if the feature has not already been requested.
If not, please describe it

+2

Integration of plugin Web applications

tyrone wyatt 10 лет назад обновлен 10 лет назад 2

Most organization use some form of Web application such as OWA, WordPress, Joomla or GLPI.

The Web applications plugin allows tickets to be associated with the web application.

The last few releases for the Web applications plugin fail to support association of ticket which is the most required feature of the plugin.

Integrating the Web applications plugin would allow myself and others to upgrade to the current version of GLPI rather than being held back.

+2

"Significant events" for objects (eg. for computer: OS install, hardware upgrade, etc.)

CDuv 10 лет назад 0

I'm suggesting the fact that GLPI could keep track of the significant events a Computer/Phone/NetworkEquipment/Printer/Room/etc suffered or gained of. The goal is to offer a clear view of what happened to it.


Examples:

For a computer:

* Computer was acquired

* OS was installed

* Faulty RAM was replaced

* HDD was "upgraded" for a SSD

* OS was reinstalled


For a Network equipment:

* Switch was acquired

* Faulty fan was replaced

* Firmware was upgraded


I must admit the initial need that made me think about this feature is for computers. Because they are pieces of hardware that "lives" the most and are what users are the more sensible to (it's what they use everyday and it's shape determine their mood/user experience), I need a digest of bad and good things that were done to it, so that I can determine if the whole computer should be replaced or if a OS re-installation could improve the user experience.


Implementation could rely on tickets with a simple "Significant event?" checkbox.

The "x was acquired" event could use financial and administrative informations from the "Management" tab.

Theses events shall be listed on a dedicated "Significant event" tab ordered by date.


I'm not sure the need is strong enough for a core integration so it'll be a plugin.

+2

Problem with rule to assign technician group

Javier Samaniego 10 лет назад обновлен 9 лет назад 1

I have a business rule that assign a technician group by category, for add and update. The group is added but i want change it.


Also the notification to the technician group is not sending in update case and I've set the notification for update ticket as "Group in charge of the ticket".

Thanks in advance.

+1

Delete style on copy/paste text in tickets

VonHut 6 часов назад 0

The goal is to be able to easily delete styles with a single click.

I even think it would be more useful to delete the default styles and add a button to paste while retaining the styles.

+1

Set impact from form

rrintoul 2 недели назад 0

It would be nice to be able to set the impact from in forms, not just urgency

+1

Ability to change the order of tasks in ticket templates

Augustin 3 недели назад 0

It could be great if we can change the position of each task in a ticket template because some tasks needs to be done before others.

+1

[Feature Request - GLPI 11] UX Improvement: Grouping items in the "Assets" menu

yann estada 1 месяц назад 0

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 !

+1

Automatic Patch/Firmware Update

Josephtabas 3 месяца назад 0

Hello Team, 


Hoping you appreciate my Suggested Feature. 

Instead of Updating GLPI in the Backend, 

We are hoping the update will be run through the GLPI Directly. We will have an option to update the GLPI once a new version is released without Configuring the backend ( for non-technical Users ).

1. System will Check for GLPI Update

2. Once GLPI has a new Version, the System will provide a button or field for the Update
3. The System will update it self without the interaction in the Server ( For non-technical Users )

Thanks, 

Regards, 

Joseph T. 

+1

Add image button on forms

VonHut 3 месяца назад 0

It would be great to improve the user experience of the service catalog to add a new type of item question in the forms.

For exemple having images instead of text to allow the user to click on one to select sub section of the forms.

it will be like having images instead of text for the Radios type.

We can do this by adding a description type with images linked to sub forms but it will increase the number of forms uselessly...

exemple of what wanted below (but without the need to have the radios button):

Image 512

+1

Add a new field ot Change type

VonHut 3 месяца назад 0

To maintain an ITIL compatibility on change management in GLPI it qould be great to add a new field of Change type for the changes.

This type of changes are described in ITIL :

  • Emergency Change
  • Normal Change
  • Major Change
  • Standard Change

So you don't have to recreate a tree sctructure with all the subcategory in each 'change type'

Сервис поддержки клиентов работает на платформе UserEcho