This idea suppose this another one Improve Search Options of IT Assets - Improvement #1 - Add denial of first conditional have been taken into account.

We all know that it is impossible to make certain queries with GLPI today. One of these queries could be the following

P11: Computers with processor Intel(R) Core(TM) i5
P12: Computers with operating system Microsoft Windows XP
P13: Computers with processor Intel(R) Core(TM) i3
P14: Computers with processor system Microsoft Windows 7
               Q11: ( P11 * P12) + ( P13 * P14)

and this question is impossible to make because Search Options doesn't allow to associate logic operator explicitly. That happens when we try to do something like that.

Example #1

We could think that A + B give us a set of 1584 computers but this is that happens

There are more examples of impossible queries but only one of them is enough to show them exists.

There are other situations where the queries are possible but they are tedious and difficult of build because you must to know Boole algebra. The following is an example of that.

P21: Computers with processor Intel(R) Core(TM) i5
P22: Computers with operating system Microsoft Windows XP
P23: Computers with processor system Microsoft Windows 7
                      Q21: P21 * !(P22 + P23)

This question is impossible to make for the same reason as before; Search Options doesn't allow to associate logic operator explicitly. That happens when we try to do something like that.

Example #2

We know that Q21 is a set of 123 computers but how can we do the query. unlike the previous situation we can transform Q21 into this equivalent query: P21 * !P22 * !P23.

And this is the current state of Search Options, although there are also situations where logical operators are associated in a capricious way giving curious results. :/

To resolve these problems I suggest the following:

This new operator '>', and its opposing party '<', will manage the associative search criterion in a explicit way. This is the idea:

This approach would allow two new features:

• Associate logical operators
• Create nested conditionals up to a fixed level

These would be the solutions to Example #1 and Example #2 with this new approach.

Example #1

Example #2

Simple, isn't it? ;)

Regards,
 

When a power supply is assigned to an phone (only possible from components, not from phone) it will not shown components)

The current behavior:

When a major incident occurs, we receive a lot of call. The best practice is to create a ticket for the first caller and add each next callers as requester to this ticket.

Today GLPI allow to setup the sending of a notification to the “requester” based on the event “ticket creation”. Which means that the first user receive a notification.

GLPI allow also to setup a notification to the “requester” based on the event “New user in requesters” but this means that

• When adding user 2, the users 1 receives a second notification and the users 2 receives a first notification.
• When adding user 3, the users 1 receives a third notification, the users 2 receives a second notification and the users 3 receives a first notification.
• And so on…, when adding 20 users to a ticket, the user 1 receive 21 notifications…

As a consequence, we may not setup the notification to added users based on the event "new user in requesters"... Only the first user is notified.

The good news is that it is already possible today to send a notification automatically to each caller when the technician solve the incident.

My idea:

by adding a recipient “last requester added" to the recipient’s notification, we would be allow to send a notification to the added users only.

In this way, each users would be informed once when calling.

Merci à Jean-Mathieu, Julien et Bazile et tous les contributeurs pour GLPI :) and thank you for reading me.

Malamort

on GLPI 9.2  

Now that glpi long awaited new website is up, it would be great to add a couple of new subforums to international support:

• Spanish
• Portuguese

http://forum.glpi-project.org/

Would be awesome to see glpi as preconfigured UCS App.

Would be more awesome, if not only users and groups are synced, but also assets (at least the network ones).

Thanks a lot,

meg

P.S. Some docs:

https://docs.software-univention.de/app-tutorial-4.1.html

It would be great when if you wanted to assign a ticket to several users, the "add" button would work two or more times without saving. To avoid clicking "add", "save", "add", "save", "add", "save"... every time.

The simple helpdesk.php anonymous ticket creation form should include an optional email address field.
This would record the same details as an anonymous ticket from email.

Instead of a month or warranty dropdown, add an end of warranty date.

Create a rules engine to link an asset, automatically inventoried wth a user

Actually we have a rule to change the status to pending when an approval is sent to compliance user. But the status does not come back to process assigned.

It should be great to add a rule when the approval is granted change the status to process assigned