Cannot save tickets when additional field is enabled

[SaillyMaxence]

Code of Conduct

• I agree to follow this project's Code of Conduct

Is there an existing issue for this?

• I have searched the existing issues

GLPI Version

11.0

Plugin version

latest

Bug description

Bug description

After updating GLPI to version 11, we encountered an issue with the Fields plugin.
When an additional field related to tickets is enabled, it becomes impossible to save the ticket — clicking the Save button does nothing.

If we disable the additional field itself (not just remove the "mandatory" option), the ticket form works normally again.
Once the field is re-enabled, the problem reappears.

It seems like there might be a missing or broken function call when the plugin tries to handle the additional field during the ticket save process.

Expected behavior

Tickets should be saved correctly even when additional fields are enabled.

Actual behavior

When an additional field is active, clicking the Save button does nothing, and the ticket is not created or updated.
Disabling the field immediately restores normal save behavior.

Relevant log output

Page URL

No response

Steps To reproduce

1. Upgrade GLPI to version 11.
2. Install or enable the Fields plugin.
3. Create or enable an additional field linked to tickets.
4. Try to create or update a ticket.
5. Click Save → nothing happens.
6. Disable the additional field → saving works again.

Your GLPI setup information

• GLPI version: 11.0
• Fields plugin version: 1.22.1
• Installation type: Docker / Kubernetes
• Database type: MariadDB
• Browser(s) tested: (please specify) : brave / chrome

Anything else?

No response

[SaillyMaxence]

we made a document with all tests ran, if u give us a mail adress, we can share it with you to help u to reproduce our problem

[RomainLvr]

You can share it at rlecouvreur@teclib.com.
Thank you in advance.

[stonebuzz]

Hi @SaillyMaxence,

Could you also provide the container type (tab / addition before the Save button),
as well as the attached fields?

Best regards,

[SaillyMaxence]

Hello,

we created a field "dsichampticket" the type is instert before saving

Inside this fields, we have multiple fields like dropdown or text (see screen below)

We put it in form like this :

To help u we've already test :

Delete and recreate list, saving button don't work,
We tried to disable and enable the plugin, issue still here,

Thanks u,

Maxence

[stonebuzz]

Sorry, I hadn’t seen your email with the information yet.

I see two important points in your message:

1. Using Fields plugin in GLPI native forms
At the moment, it isn’t possible to use fields from the Fields plugin in GLPI’s native forms, unlike what was possible with Formcreator.

You can use the dropdownq (as you did), but they won’t be applied to fields added via the Fields plugin (only inot ticket descirption ATM). This is because GLPI itself shouldn’t handle this, as it would create a dependency between GLPI and the Fields plugin, which we want to avoid.

This functionality is currently under development on our side and will be available soon.

2. Ticket saving issue when the Fields plugin is activated

A fix (related to dropdown field) is in progress and should be proposed shortly.

[SaillyMaxence]

Do u have a date for this fix ? or we have to rollback to glpi10 ?

Thanks u

[stonebuzz]

Ticket saving issue when the Fields plugin is activated
The fix is in progress and should be available shortly (today or tomorrow).

Using the Fields plugin in GLPI native forms
This feature is also in progress, but I don’t have an estimated date at the moment.

[SaillyMaxence]

We just made a test,

We disabled the dropdown field, and only kept classic text field, the plugin and save button work correctly,

If the dropdown is fine we can use the plugin.

One last question, when u said GLPI native forms

Our users use the page "Catalogue de service" with différents forms like this one :

If we put the field dropdown after ur fix, it's gonna work or this is ur first point (1. Using Fields plugin in GLPI native forms)

[stonebuzz]

No, the fix for the Save button only addresses the ticket form.

Form questions related to Fields plugin dropdowns work, but the answers are only added to the ticket description, not to the corresponding Fields plugin fields.

[SaillyMaxence]

Thank you for the explanations, we’re waiting for your correction

[stonebuzz]

Hi @SaillyMaxence

can you try this -> #1050

Best regards

[SaillyMaxence]

Hello,

We just make a test, with modification it work, thank u,

If u have a date for the first 1. Using Fields plugin in GLPI native forms we’d be glad to know