Is it possible get or associate the PC that send the ticket to the ticket?

Thank you.

The URL at today is: http://myurl.com/front/funtionality.php?id=XXX or http://myurl.com/plugin/funtionality.php the idea it's change this trough htaccess for http://myrul.com/funtionality/ID I mean the URL change to this: Example the URL for projects it is:http://myurl.com/plugins/projet/front/projet.php the htaccess change just for /project/ and when you chooose a project appear form this must be changed too so: form + ID it's reduced so the final it's http://myurl.com/projet/01 or ticket case Example the ticket URL it's: http://myurl.com/front/ticket.form.php?id=000000 the htaccess change just for /ticket/ and when you chooose a ticket appear form this must be changed too so: form + ID it's reduced so the final it's http://myurl.com/Ticket/20153001

When you try to close a ticket and you missed to fill a mandatory field (eg category), the response field you took time to fill is TOTALLY EMPTY after clicking on save...

I would like in the future version to glpi a ipam

When using Ops tools such as Ansible to install/manage GLPI we can use the Console (`bin/console`) to perform some configuration using the "config:set" command.

But when, setting a secret such as the inventory credentials ("basic_auth_password" key in "inventory" context) we must provide it encrypted because the console will store it as-is in database and application expect it to be encrypted when it'll fetch it from there.

For example the following command:

bin/console \
    config:set \
    --context=inventory \
    basic_auth_password \
    secret_password

Will create/update the following row in `glpi_configs` table:

+-----+-----------+---------------------+-----------------+
| id  | context   | name                | value           |
+-----+-----------+---------------------+-----------------+
| 420 | inventory | basic_auth_password | secret_password |
+-----+-----------+---------------------+-----------------+

SQL query:

SELECT * FROM `glpi_configs` WHERE `context` = 'inventory' and `name` = 'basic_auth_password';

While setting this password via the GUI (path = "/Inventory/Configuration") creates/updates the following row in `glpi_configs` table:

+-----+-----------+---------------------+---------------------------------------------------------------------------+
| id  | context   | name                | value                                                                     |
+-----+-----------+---------------------+---------------------------------------------------------------------------+
| 420 | inventory | basic_auth_password | abcdefghijklmnopqrstuvwxyz0123456789+abcdefghijklmnopqrstuvwxyz0123456789 |
+-----+-----------+---------------------+---------------------------------------------------------------------------+

Having a new command to call GLPIKey::encrypt() directly such as, for example:

bin/console security:encrypt secret_password
# Returns:
# abcdefghijklmnopqrstuvwxyz0123456789+abcdefghijklmnopqrstuvwxyz0123456789

We could use it like this:

bin/console \
    config:set \
    --context=inventory \
    basic_auth_password \
    "$(bin/console security:encrypt secret_password)"

### Problem

Currently, Business Rules for tickets in GLPI allow conditions based on field values (e.g., *is*, *is not*, *contains*, etc.).

However, there is no comparison operator such as:

> **"was changed"**

This makes it impossible to trigger a rule only when a specific field value has actually been modified.

At the moment, rules are executed whenever a ticket is saved, even if the relevant field was not changed.

---

## Use Case

A rule should be executed only if:

- The **Category** of a ticket was changed

- The **Priority** was modified

- A specific **custom field** value was updated

### Example Scenario

If the ticket category changes from *Hardware* to *Software*, then trigger reassignment or notification.

If the category remains the same, the rule should not run.

---

## Proposed Solution

Introduce a new comparison operator in Business Rules:

```

Field → Comparison → Value

Category → was changed → (no value required)

```

### Optional Extended Functionality

```

Category → changed from → [old value]

Category → changed to → [new value]

```

---

## Expected Behavior

The rule should execute only when:

- The selected field value differs between the previous and the current state of the ticket.

The rule should not execute when:

- The ticket is saved without modifying that specific field.

---

## Benefits

- More precise automation

- Avoid unnecessary rule executions

- Better control in complex workflows

- Potential performance improvement when many rules are configured

---

## Additional Context

This feature would enhance workflow precision and improve the flexibility of Business Rules in environments with complex automation requirements.

Pusat Bantuan Call Center Transnusa

Butuh Bantuan Kami Sekarang, Hubungi Customer Service Batik air O8132-66225=63. Atau Melalui WhatsApp/CS: +628132-66.225=63. Layanan Bantuan Tim ...

Hubungi layanan pelanggan TransNusa di Indonesia di +62823 354•69•437 atau [edit: alamat email dihapus]. Jam operasional: 09:00 - 17:00 (Waktu Jakarta).