Currently when viewing a KB article the header is displayed as follows:

Subject

A Very Interesting Article

Content

My very interesting article content. Blah blah blah....

The subject is not formatted in any way like an article title and I often find myself creating a further title in my Content area formatted with H1 tags.

I would prefer it if we did not waste space at the top of the viewable version of the KB article by including the works Subject and Content, instead it would be preferable if the header same header as above were formatted as follows

A Very Interesting Article

My very interesting article content. Blah blah blah....

Hello,

The mail collector does not use the proxy informations for connection to the IMAP server.

Please, could you add this missing functionality ?

With kind regards

Please add Email Notify to Owner or someone when an Asset "Status" or "owner" are changed.

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?