Good Morning,
It would be nice to have a data dictionary available directly in the application.

It would also be interesting to have a simpler way to connect the glpi to the powerbi or similar to make comparisons between calls and working time to buy if slas are being long and if it is a technical hour this is compensating.

GLPI 9.3.3 version.

I need to render one of the existing fields on computer, in mandatory field.
the field is a drop-down list.

how can i do that on php code?

Hi

Please is it possible to add a feature about credit and debt of department devices and record the department assigment story:

For example: Customer service fires an employ, computer and monitor are moved to IT warehouse and Customer service dept has a monitor and a computer credits because devices bought with its budget; backoffice hire a new employ and IT provides them the ex customer service devices and the department has devices debt, when customer service need devices, IT buy them on backoffice budget to repay the dept.

I hope it's clear

Thanks and best regards

Stay safe in this period.

Hello, 

I have a feature request from my users where we put the manufacturer and type instead of on the device itself on the model for the device so they don't have to fill it out every time there is a new device only when there is as new model

Thank you

Is your feature request related to a problem? Please describe.

In https://github.com/glpi-project/glpi/pull/7183 database backup was droped, because it was very slow and works only for very small databases.

Describe the solution you'd like

I think it will be good to use https://github.com/ifsnop/mysqldump-php or system mysqldump to dump database.

Describe alternatives you've considered

Alternatively the backup task can be triggered by cron job with tools mentioned above.

1. User clicks backup button in web ui.

2. Automatic action for cli created.

3. Cron triggers backup job.

4. Backup starts in cli process.

Hello,

Would it be possible to make the change view as configurable as the ticket view as to allow a certain profile to onyl see the tickets that is either attributed to a user, a group/profile ?

The only options are to see the changes on which you are author or all changes.

it is not possible to use the search engine to search date indicated in the future.

for exemple, if I want to search for certificate that will expire soon, it is not possible to indicate in the search engine a relative date like +2MONTH as only negative relative date are present

to do so, it can be easy based on how GLPI is built, just add the following in inc/html.class.php :

for ($i=1; $i<=12; $i++) {
$dates[$i.'MONTH'] = sprintf(_n('+ %d month', '+ %d months', $i), $i);
}

right after :

for ($i=1; $i<=12; $i++) {
$dates['-'.$i.'MONTH'] = sprintf(_n('- %d month', '- %d months', $i), $i);
}

the rest will do the job

In last version of webservice plugin can call listObjects and getObject only admin user. This makes this plugin useless for security aware company.

For example. If I want to integrate GLPI for example with ansible I can do it using glpi_ansible (https://github.com/Webelys/glpi_ansible) This ansible plugin calls listObjects and getObject and stores credentials in text file. Due to limitation of web service plugin I have to create service account in GLPI with administrator privileges. When servers administrators which are using ansible are not GLPI administrators, the they will got credentials for administrators access to GLPI and this is BAD.

Allow use listObjects and getObject for non admin user and control access to object types according standard GLPI rights.

As you can see filenames are cut quite short for optimal display.

It shows "Configuring the Exist..."

Other columns, like Mime type, allow full (or at least) bigger names without trim.

It would be nice if the field was bigger, or even configurable.

It is better to transfer charecteristics of models in properties of Component then describe them every time / Лучше перенести характеристики моделей в свойства Компонента, чем описывать их каждый раз