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

+1

Time Based Contract

Grooby hace 2 años 0

Some contracts are for a specific number of hours. for example. I sign a contract in which I provide 30 hours of services. It would be great if you could add this type of contract.

Regards :)

+1

GLPI 10.0.2 - Cloning - Proposed additional options

Loudgi hace 2 años 0

Hello,

Since my passage under GLPI 10 with the migration of the pluggin, there is no longer the possibility of cloning a ticket with its Requester, Group, its attachments, which can be tedious to inform at each cloning.

Do you think this could be a future integrated feature? A priori we had it formerly with GLPI 9.2 and the plugin.

Regards

+1

Add Remote Control for RDS (Remote Desktop Service) / MSRA (Microsoft Remote Assistance) - Putty

TOFR710 hace 2 años 0

La version 10 de glpi permet d'ajouter des éléments de control à distance pour des ordinateurs (Teamviewer, AnyDesk...)

Ne serait il pas possible d'ajouter RDS et MSRA ? et éventuellement Putty

Aujourd'hui, pour ajouter cette fonctionnalité, il faut passer par les liens externes  https://forum.glpi-project.org/viewtopic.php?id=282281 et déployer des clés de registre.

+1

Ticket: method to switch to the correct entity

abm hace 2 años 0

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

+1

Contracts: Add an Internal Notice field

Mathieu MD hace 2 años 0

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.

+1

Clone reminders

Maëva hace 2 años 0

hello, 

Allowing the cloning of reminders with the same information

+1

spell check

Will hace 2 años actualizado hace 2 años 4

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

Image 407

+1

Hide pane Tools (personal reminders and rss feed)

F4t4lid4d3 hace 2 años 0

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

+1

Option to add custom assets in the list

Manoj hace 2 años 0

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...

+1

Add ISCSI storage type in agent's json parser

Enrico Ghera hace 2 años 0

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 :-)