New ticket screen get refreshed reach time actor is changed

kyalpha · 2022-06-21 10:45:19

On new ticket screen, it's understandable that when I change Type or Category of the ticket, it's trying to load ticket template and reload the page.
But When i'm changing the Requester/Observer/AssignedTo, the screen also get refreshed. I feel frustration when trying to add multiple observer.
Is there a config for this?

kyalpha · 2022-10-17 08:16:31

kyalpha wrote:

On new ticket screen, it's understandable that when I change Type or Category of the ticket, it's trying to load ticket template and reload the page.
But When i'm changing the Requester/Observer/AssignedTo, the screen also get refreshed. I feel frustration when trying to add multiple observer.
Is there a config for this?

Still looking forward for an answer...

cconard96 · 2022-10-19 20:27:43

I cannot recreate that issue. I can click in any of the actor fields and select a user/group multiple times. The page doesn't refresh until I hit save and create the ticket.
This is with the latest 10.0 bugfixes branch.

Rafumel1774 · 2022-10-19 20:56:49

What?! I can confirm and was always annoyed but thought this is normal!
@cconrad96 - please note it is only on the CREATE TICKET page. The tech will be added to the requester. When you remove him by backspace the page gets reloaded. When you add somebody the page is reloaded too.

Kallisti · 2023-05-18 12:47:34

Hi - I just found this post looking for an issue to follow.

We have the same behaviour in our environment. Any change to the actors on the create ticket page leads to a full page reload.

We're on 10.0.7 and it's been like this since we upgraded to version 10. Happy to provide further details!

cconard96 · 2023-05-18 13:09:17

I confirm the behavior for new tickets. I do not know how I missed that before. I'm not sure the purpose, but this behavior was explicitly changed for new tickets/changes/problems when the UI was changed for GLPI 10.
The actor field template contains:

{% if item.isNewItem() %}
   {% set onchange = 'this.form.submit();' %}
{% endif %}

Kallisti · 2023-06-08 20:12:22

There is an issue for this behavior now.
https://github.com/glpi-project/glpi/issues/14881
There is a proposed fix that will keep the behavior for requester but change it for the other actors.

cconard96 · 2023-06-09 01:57:54

The proposed fix is the best possible solution at the moment. At some point, the new data may be able to be retrieved over AJAX but that is a complex change and wouldn't be good for a bug-fix release.

repentandliveholy · 2023-09-18 10:19:44

How can it be fixed?

repentandliveholy · 2023-09-18 10:25:52

cconard96 wrote:

I confirm the behavior for new tickets. I do not know how I missed that before. I'm not sure the purpose, but this behavior was explicitly changed for new tickets/changes/problems when the UI was changed for GLPI 10.
The actor field template contains:
{% if item.isNewItem() %}
   {% set onchange = 'this.form.submit();' %}
{% endif %}

could this code be fixed?

cconard96 · 2023-09-18 13:34:41

It isn't broken. As I said, the code clearly shows the behavior is intentional.
If you mean the reloads just when changing observers and assigned techs, then it was already changed for 10.0.8.

repentandliveholy · 2023-09-18 13:58:59

yes, it works correct when changing\adding an observers or assigners, but not when requester.

what can we do to form not to be refreshed when adding\removing\changing a requester?

it is very important for us, because not all the users use forms to make a new ticket, but we or a person who responsible for acceptinn a new tickets needs to put it his or her(requesters) name.

is it possible to manually change this code page not refresh evert time?

or may be is it possible to make a new simple form for new ticket with possibility to choose a requester as it is when editing a simple ticket form of user

thanks

cconard96 wrote:

It isn't broken. As I said, the code clearly shows the behavior is intentional.
If you mean the reloads just when changing observers and assigned techs, then it was already changed for 10.0.8.

Last edited by repentandliveholy (2023-09-18 13:59:57)

repentandliveholy · 2023-09-18 16:02:22

also the same thing with changing categories..

cconard96 · 2023-09-19 01:43:09

There is a reason the page refreshes. The new selections need sent to the server to recalculate things like determine if a new ticket template needs applied or if the valid entities needs changes (in the case of changing the requester).
To expand on "At some point, the new data may be able to be retrieved over AJAX but that is a complex change and wouldn't be good for a bug-fix release.":
Currently, data like templates is computed when the form is loaded so reloading the page is required. Changing the code to work without a page reload will require a lot of changes to a complex part of the code for tickets, changes and problems.
That means it has to wait for a major release like 10.1 or 10.2, and also wait for a developer to have time available to work on it.

Any manual change to the code to prevent the reload would break the ticket templates, entity assignment and probably some other features.

repentandliveholy · 2023-09-19 08:29:27

Thank you very much for explanation. Yes, I got an idea that for now it is necessary. But, as you said, we can wait in future an update in which it would be made in other way, so that it would be needed to reload a page every time? If so - it is very good new and we wiil look forward for this update!

cconard96 wrote:

There is a reason the page refreshes. The new selections need sent to the server to recalculate things like determine if a new ticket template needs applied or if the valid entities needs changes (in the case of changing the requester).
To expand on "At some point, the new data may be able to be retrieved over AJAX but that is a complex change and wouldn't be good for a bug-fix release.":
Currently, data like templates is computed when the form is loaded so reloading the page is required. Changing the code to work without a page reload will require a lot of changes to a complex part of the code for tickets, changes and problems.
That means it has to wait for a major release like 10.1 or 10.2, and also wait for a developer to have time available to work on it.
Any manual change to the code to prevent the reload would break the ticket templates, entity assignment and probably some other features.

Forum GLPI-Project

Announcement

#1 2022-06-21 10:45:19

New ticket screen get refreshed reach time actor is changed

#2 2022-10-17 08:16:31

Re: New ticket screen get refreshed reach time actor is changed

#3 2022-10-19 20:27:43

Re: New ticket screen get refreshed reach time actor is changed

#4 2022-10-19 20:56:49

Re: New ticket screen get refreshed reach time actor is changed

#5 2023-05-18 12:47:34

Re: New ticket screen get refreshed reach time actor is changed

#6 2023-05-18 13:09:17

Re: New ticket screen get refreshed reach time actor is changed

#7 2023-06-08 20:12:22

Re: New ticket screen get refreshed reach time actor is changed

#8 2023-06-09 01:57:54

Re: New ticket screen get refreshed reach time actor is changed

#9 2023-09-18 10:19:44

Re: New ticket screen get refreshed reach time actor is changed

#10 2023-09-18 10:25:52

Re: New ticket screen get refreshed reach time actor is changed

#11 2023-09-18 13:34:41

Re: New ticket screen get refreshed reach time actor is changed

#12 2023-09-18 13:58:59

Re: New ticket screen get refreshed reach time actor is changed

#13 2023-09-18 16:02:22

Re: New ticket screen get refreshed reach time actor is changed

#14 2023-09-19 01:43:09

Re: New ticket screen get refreshed reach time actor is changed

#15 2023-09-19 08:29:27

Re: New ticket screen get refreshed reach time actor is changed

Board footer