Glpi API REST returns tickets with its actors.

but there is no indication about each actor role :

Wich actor is requester, observer or technician ?

these roles would be usefull.

Hi,It'd be great to be able to minimize and maximize categories when creating a ticket. In the case, we use a lot of categories and we don't want to expand all by default.

text in column is left aligned and text is centered in column header, this is sometimes a bit confusing.

Is think header should have same aligment than its column

http://forum.glpi-project.org/viewtopic.php?pid=330393#p330393

Add an adapter for RocketChat (https://rocket.chat/).

The adapter can perform the following :

• get info from a specific ticket
• get all the open tickets
• get all tickets from an operator
• get all tickets from an user
• ...

Thanks

We have over 1000 usb mouses in our consumables, since reaching that 1k mark the action button disappeared because of "too large selection" even when you have for example 50 position display setting. I think this bug is connectet to the paging feature implemented not so long time ago.

It would be great to be able to search for projects and project tasks in the global search.

When the list of VLANs is large scroll it manually is uncomfortable.

Would it be possible to add a column in main page "number of assigned licenses"? I would like to use it to create a simple license balance.

Dear GLPI Staff. Best Regards. Is it possible to integrate Slack natively into the GLPI?

Possible Uses:
- The number of Channels would be made at the Reason of the Categories or Entities
Being

able to make use of the Bots so that they search in each channel would

look for objects related to this such as computers, incidents, devices

people etc.
Be able to use bots that can read the knowledge database and suggest things to us within the channel or recursively
Be able to use BOTS to suggest information such as possible tasks to create, documents and other objects
Be able to use BOTs that support projects, suppliers, contracts and SLAs.
That is to say Enable reading the different options, API and interaction with SLACK as best as possible.

when creating ticket by web interface, ticket is created in the requester entity( it makes sense if only one entity)

there is no rule to assign entity for mailgate : ie :

criteria : collector is my collector

action : assign requester default entity ( or assign requester 'first' entity)