In Older versions (9.5.7 and olders), the ticket's writer (a technician of the central helpdesk with recursive rights and positioned at the "parent" entity in our case) could select a requester in the appropriate drop-down regardless of the entity membership of the requester (all users of all entities displayed in the drop-down). When the requester had muliple authorizations, it was possible to choose the entity in a second drop-down

In version 10.0.0, in the ticket's form, the ticket's writer has to first select the entity to be able to see the user in the drop-down. It was so appreciate to be able to select a user without first have to know obligatorily the entity membership.

It seems to be a regression or is it a bug ?

Thanks for your help

Current Notice field is not enough. Most organizations need two timings:

1. Notice, which is the official delay required by the supplier to renew the contract (by example 2 months);
2. Internal Delay, which is the time required by the organization to handle and prepare the renewal (hierarchy approval, validation process, etc.) (by example 3 weeks).

Currently, we have to merge both delays into the single Notice, but doing so 1) we lost the official delay, and 2) we have to round up delays (being unable to pick days but only months).

That's why I think adding a second Notice field (which could be name Internal Notice) would help to better manage contracts.

hello, 

Allowing the cloning of reminders with the same information

On GLPI 10.0 you cannot right click and amend spelling. It would be good to integrate a dictionary of sorts. 

Hide pane "Tools" (personal reminders and rss feed).

Hi Team,

Is it possible to add an option where we can add custom asset names like DVR, Attendance machine, Laptops, MAC, SIP phone, Server, etc...

i just tried to run the v1.4 agent on my servers and got the following output:

[info] sending contact request to server0
[info] sending prolog request to server0
[info] running task Inventory
[info] New inventory from pve-enc0bl01-2022-08-02-12-13-36 for server0 (tag=enc0bl01)
[error] [http client] communication error: 500 Internal Server Error
[error] [http client] server error: JSON does not validate. Violations:
"ISCSI" does not match to ^(SCSI|HDC|IDE|USB|1394|SATA|SAS|ATAPI)$ at #->properties:content->properties:storages->items[1]:1->properties:interface

that makes sense as some of my lvm volumes are hosted on a HPE MSA2040, which is accessible through ISCSI

I think that ISCSI is a type of storage worthy of being counted in the standard types

please add it :-)

Olá!!

Gostaria de saber se é possível integrar o GLPI com o Jira.

Quando um usuário cria um problema no Jira, quero ver os ativos que pertencem a ele. Isso é possível?. Como eu posso fazer isso?

desde já, obrigado

Our GLPI server is currently configured to send us (the IT pole) the notifications "internally", that is to say that it uses the SMTP connector of our local Exchange server (which is completely cut of the net). The advantage is that users can only view the notifications internally. That said, if there was a way for GLPI to send notifications to IT teams on external emails, it would be a real plus! That would allow, for the data processing specialists, in this type of configuration a follow-up of the notifications of creation of ticket out of the walls of the company.

A request for the possibility of adding components to tickets - they are purchased separately or replaced, and it would be good to have the possibility of connecting such a separately purchased disk, memory chip, graphics card as an item to the ticket.

Actually, components should be full-fledged items.