There is no way to specify a contract End Date to a given day. You set a Start Date and pick a number of months in Initial contract period, then the End Date is computed. But we have some contracts that doesn't matches this algorithm.

I think that implementing one of these options would enhance Contracts management:

• adding a dedicated End Date field
  • (which could be prefilled by JS according to Initial contract period, so that user experience would not change); or
• allowing to pick a Initial contract period in days instead of only in months.

We would need a new category called Storage under Assets. It would be easy to maintain our NAS like Synology and NetApp.

How to assign a line to a phone?

Bonjour,

J'ai vu différent post concernant la gestion des cartes SIM mais je trouve ça vraiment complexe.

Pour ne pas simplement créer toutes les entrées liées aux cartes SIM dans Configuration/Composants/Carte SIM

Il n'y aurait qu'à créer une nouvelle entrée via le bouton +, et de renseigner directement code PIN1, PIN2, PUK1, PUK2, N° téléphone etc. Puis de l'associer au téléphone souhaité. 

Actuellement, je ne comprend pas pourquoi il faut d'abord créer un template, pour ensuite ajouter des cartes SIM dans Éléments ?

De plus je ne vois pas non plus l'utilité de créer une "ligne" pour chaque SIM étant donné qu'un N° est directement lié à une carte SIM. 

New major builds have multiple release candidates and beta releases in a attempt to minimise bugs before the stable build is released.

Minor builds on the other hand don't have beta releases and often introduce new bugs.

Can you release a beta release of minor builds a few weeks before the stable build is released?

Myself and other non developers in the GLPI community would be happy to setup a staging site to test compatibility and look for new bugs.

Notification about not resolved tickets from some entity will sends not to some profile/group/etc., but to the person(technician’s), who are mentioned in ticket, like an assigned to, or to entity/group administrator. And only those tickets, which already due date expired.

It would be nice if we have a new ticket status called reopened for all reopen tickets

Context: I use the Documents (from Management) to store some user manuals, technical specifications, firmwares, utility softwares about my computers, network equipment, printers, etc.

If a technician needs the user guide about the computer he is repairing he does not have to look on the Internet or find the physical manual (if any): he just goes to the "Documents" tab of the asset.

This solution works fine but have a major drawback: documents can be associated to single/individual asset. So if I have three servers of the same model (eg. BrandX SupermodelY) I'll have to associate my user manuals to theses three assets. If in the future I acquire a fourth SupermodelY server: let's hope I won't forget to associate it to my user manuals.

What I suggest is the ability to associate a document to some dropdowns, for examples:

• The models (Computer models, Networking equipment models, Printer models, Monitor models, Peripheral models, Phone models).
• Virtualization systems
• Operating systems

Then, I'll associate my BrandX SupermodelY user guide to the "BrandX SupermodelY" computer model, and any past or future computer asset that is of model "BrandX SupermodelY" will have the user guide listed in it's "Documents" tab.

As an implementation reference: it is already possible to associate documents to "Locations" (but, where it differs from my idea, is that I don't see any implication on assets set on that location).

Add the possibility to archive an item.

An archive is a new state, as it is for deleted items.

The simple way is to add a is_archived field, and filter the view in the asset's search engine.