Possibilité de modifier les tickets directement depuis le listing des tickets avec le module 
X-editable Demo (vitalets.github.io) ?
Plutot que d'ouvrir chaque ticket et modifier le statut par exemple.

Hi all,
It would be great if two hooks were added on the formatUserName function of the inc/dbutils.class.php file.
Something like : 

Plugin::doHook("pre_format_username", [
            'ID'           => $ID,
            'login'        => $login,
            'realname'     => $realname,
            'firstname'    => $firstname,
            'link'         => $link,
            'cut'          => $cut,
            'force_config' => $force_config
      ]);

AND

Plugin::doHook("post_format_username", [
            'ID'           => $ID,
            'login'        => $login,
            'realname'     => $realname,
            'firstname'    => $firstname,
            'link'         => $link,
            'cut'          => $cut,
            'force_config' => $force_config,
            'username_substrings'=>[
                'before'    => &$before,
                'formatted' => &$formatted,
                'after'     => &$after
             ]
      ]);

Thi is not perfect, just an idea to avoid people having to edit the core files when they want tu customize the display.

Add a date_mod column to the glpi_tickets_users table so there is a source other than glpi_logs to retrieve a ticket assignment timestamp for a specific user from. Currently you  have to join 3 additional tables to yield an average time-to-solve per user. This could be alleviated by storing the assignment date in the glpi_tickets_users entries.

It is not clear why we have three different user/group entities attached to projects/tasks.

Would it not be better to allow users and groups to be added to the Project Team and allow the following Project roles to be assigned to users in the project team Project Manager, Project Sponsor,  Project Team Member (default).

Tasks ownership should only be able to be assigned to a user in the Project Team.

sub-project team membership and roles should only be able to be assigned to members of the parent project team.

Currently Kanban splits tasks/projects into columns for task/project status, it would make project management simpler if it were also possible to switch to each of the following views.

Put tasks/projects into separate Kanban columns for each project/task user/owner

Put tasks/projects into separate Kanban columns for each project/task group

This would allow simple reassignment of task to different users/groups by drag and drop.

Hi, i search how can i synchronize contacts from the crm dolibarr to glpi.

I found a plugin in the glpi market  "glpi to dolibarr" but it's not what i'm looking for. Someone have an idea about to help me please??? Thanks

We would like for users to be able to register for access where they would create their own username and password. For 10 version, this gonna be a feature of GLPI?

User story: making our first steps with the planning, we had all "event types" checked. Thus, we struggled at understanding why the tasks we actually planned were still not shown. To make our tasks appear, we had to untick one of the checkboxes, which is a surprising behavior.

Procedure : Go to Home / Assistance / Planning, and check all boxes in the "events type" panel

Expected results : all events are shown on the calendar.

Actual results : the events we were looking for are hidden, despite their boxes beeing checked.

Suggested enhancement :

- use a single behavior for all items in the event type list (ie, events should be shown when the boxes are checked, and hidden when the boxes are empty)

- remove the "only background events" filter, and replace it with a "background events" filter

norte se ejecutan las reglas, he creado 1 regla que debe asignar a un grupo cuando la categoría tenga una palabra en especifico pero no sirve.

It would be nice to be able to link problems to not only individual items but also device models. That way you can keep track of problems impacting an entire category of items without needing to individually link and unlink all the items.