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

0

Add "Financial and administrative information" for documents

Simon 6 лет назад обновлен 6 лет назад 1

It would be great to add "Financial and administrative information" tab for documents. 

In that way, we could link a document to a budget !

Example : I have a 1000$ maintenance on a server. I can add the invoice linked to my server (in the documents tab). And then, with this feature, I can activate "Financial and administrative information" for this document in order to link it to a budget? 

0

Management by priority (Queue position)

TGr 6 лет назад 0

Add a possibility management of tickets by priority (Queue position). This could be manage within a group.


User who submitted a ticket could see the rank of his request within the assigned group.


The queue position would be influenced by priority and other parameters that could be configurable (Very urgent and urgent could bump lower level of priority)





0

Models Notification

EC2311 6 лет назад 0

Hello

When creating/updating models (projects, tasks) no notification should be sent : perhaps for some they must be sent.

So in notification, allowing to manage sending or not of notifications of projects, tasks and so on...

0

Suggestion - Include annotation box

Júnior 6 лет назад 0

Hello, 

It would be interesting to include a notepad in Computers - Assets.
Some machines we can not always put in inventory for some reason and a notepad in that GLPI session could help remind you why not include or which machines are missing from inventory.


Thanks!


0

Retrieve additional user data through phpCAS

ojathelonius 6 лет назад 0

Currently, CAS authentication only retrieves the user login through phpCAS.


It would be awesome to have a way to get more data from the single sign-on server, e.g :


/* Current behaviour in getAlternateAuthSystemsUserLogin() */
$this->user->fields['name'] = phpCAS::getUser()
/* Desired behaviour */
$additionalAttributes = phpCAS::getAttributes();
$profile = additionalAttributes['cas_profile_key'];


Ideally, the user should be able to map GLPI user data with CAS data, just like with external auth.


I worked on a solution but it is limited to my own use case thus is not quite generic. I would love to help though.

0

Assets: Add views of items to show to favorites

steckel 6 лет назад 0

only saved searches possible, like to have that for items to show as well

0

Filter emails from lists

Megachip 6 лет назад 0

Ho to filter all mails from mailing lists? 


There are headers like:

Precedence: list
Mailing-list: list
List-ID:

But how to filter for custom headers?

0

Have the date field in tasks

gmourani 6 лет назад обновлен informatica 3 года назад 1

Sometimes, tasks are registered on different days that they were executed. For this reason, it will be nice to have the date field in tasks to put the real task execution date (otherwise it used the current date).

0

Screen Customiser

tghuverd 6 лет назад 0

Being able to non-programmatically change field names, hide field names, change the one-line field help text, move fields around on the screen, reorder the <tab> key sequence, and add fields to screens is a common Administrator capability in current generation Asset Management software.


This does not require editing PHP, locales files, or the underlying database, but is done within the application using a visual editor interface via the browser. These changes survive a version upgrade, so need to be considered an overlay to the standard field labels and layout.


The editor allows for changes globally - so that every instance of "User", for example, is changed - or locally to a particular screen only - so "User" in the Computer screen only, for example.


It also supports adding and labeling a small number of 'custom fields' per screen. These custom fields come pre-established within the GLPI database, but remain unused unless the Administrator exposes them. There is a set/known number of them, so there might be:


- 5 * Text Field

- 5 * Numerical Field

- 2 * Dropdown

- 2 * Date


(These are an example only)


The Administrator might then use the Screen Customizer interface to expose (and label) 3 * Text and 1 * Date on a particular screen to capture customized user input. Presenting the captured data is via a customized report(s), but note that manipulating the fields is via code. So, if the Administrator wanted to compare an existing GLPI date field with the customized date field, they would have to write PHP code to do this.


Such a screen customizer would greatly improve the utility of GLPI, by making it easier and faster to tailor the user interface to business requirements. It represents a robust and enduring method of changing the screens that does not force Administrators to risk their operational instance editing code or .po files.

0

Queued Notifications table should have a notifications_id column

Valentin 6 лет назад 0

I am currently debugging an issue in regards some emails not being sent.

sent_time appears NULL for  many of the queuednotifications entries and they seem  to stay like that.

For debugging and reporting purposes,I think that  the queued notifications table should also contain the notifications_id information as currently is very hard to know which notification type generated the queued entry.

I think that notifications_id would be more important that notification_template, because we can find out the template from notifications_id but not the other way around.

Сервис поддержки клиентов работает на платформе UserEcho