Closed wc55 closed 2 years ago
Hi
A fix has already be created. Try it and feedback : https://github.com/pluginsGLPI/formcreator/pull/2914
Hi
After applying the corrections, I used the "Cancel" button and the trash can icon button
The ticket goes to the trash but remains on the self-service user's assistance home page
Should this happen?
Self-service profile:
Super Admin profile:
Hi
When a ticket is sent to the trash bin, the issue should be deleted from the database. I need to reproduce to see what happens.
I found the problem. Try the above patch and feedback.
Hi
Resolved the issue of cancellation and not showing to the user, but I tested the restoration, and the requester did not have access.
I canceled a ticket, and it showed up in the trash. Accessing the ticket in the trash, it appears that the message "Item Not Found".
Ticket in the trash:
After accessing (self-service profile):
Super-Admin Profile:
Restore by super admin. Super admin screen:
After restoring, the ticket does not appear for the requester.
Super admin screen:
Historical:
Hi
I canceled a ticket, and it showed up in the trash. Accessing the ticket in the trash, it appears that the message "Item Not Found".
When you are using teh service catalog you should not have access to the tickets list. I found that 3 redirections were missing in the plugin, which were present in versions 2.12.x. I added several comits to fix this and other inconsistencies when running your workflow.
Revert the patch you applied, download it again and apply it. You will very likely get an error when patching a file in the test/ folder. You can ignore patching this file.
Hi
I will take the test this afternoon.
Hi
I did some tests.
On tickets opened after applying the fix, when the self-service user cancels the ticket, it is no longer displayed to the user, but appears in the recycle bin for the super-admin.
If the super-admin restores the ticket, it reappears for the requester.
This was fixed, and I even did some tests in which the super-admin does the cancellation and the ticket does not appear for the requester, and doing the restoration, it appears again.
I'm just mentioning, because doing the same actions on tickets that were already open before the update, when the super-admin does the restore, the ticket actually appears again for the requesting user, but if the super-admin makes a new cancellation and a restore, the ticket does not reappear for the requester.
In summary, in old tickets, when the first deletion and the first restoration are done, there are no problems, after the second restoration, the ticket does not appear for the requester again.
On new tickets (after applying version 2.13.0), cancellation and deletion can be done multiple times and the ticket is always displayed again to the user after the restore.
Thanks
Hi
I'm just mentioning, because doing the same actions on tickets that were already open before the update, when the super-admin does the restore, the ticket actually appears again for the requesting user, but if the super-admin makes a new cancellation and a restore, the ticket does not reappear for the requester.
Was the ticket in the trash bin before you apply the update ?
EDIT : also, do you still ave such old ticket that you did not yet restored, deleted the restored again ? Sone data from the DB may be useful to understand where the problem comes from.
Was the ticket in the trash bin before you apply the update ?
Yes, the ticket was already in the trash before applying an update.
I'll test with tickets that were open before applying an update, but that weren't in the trash.
EDIT : also, do you still ave such old ticket that you did not yet restored, deleted the restored again ? Sone data from the DB may be useful to understand where the problem comes from.
I have some tickets that are still in the trash since before I applied the update, I can try to see how it is in the DB.
Which tables should I look at?
Hi
For a given ticket
When a ticket is in the trash bin the associated issue is deleted. When the ticket is restored, the issue is recreated. When both events occur, the status of the matching form answer (it it exists) is updated depending on all tickets associated to it.
Knowing all these functional rules you may detect of there is an inconsistency in the database. Actually the patch fixes the plugin to match the above behaviour. There were several problems, mostly related to the update on the table glpi_plugin_formcreator_issues.
Hi
Forgot to answer, but I couldn't find any inconsistencies.
I will do more tests
Thanks
Hi
If you don't find any inconsistency in the DB then I guess we can close this issue and merge the fix.
hi
I did not identify inconsistency, I believe it can be finalized
Hi
Thank you for your feedback. The fix has been merged.
Describe the bug The "Put in trash bin" button is not working. When the self-service profile user clicks this button, no action is taken on the ticket and nothing different appears in the log either.
To Reproduce Steps to reproduce the behavior:
Expected behavior The ticket should have the status changed or cancelled.
Screenshots
GLPI / Plugins (please complete the following information):
Instruções de instalação e configuração
Server
GLPI constants
Libraries
LDAP directories
SQL replicas
Notifications
Plugins list
Desktop (please complete the following information):
Additional context
The "cancel" button on that same screen is also not working.
I also opened an issue about the problem with the cancel button.
The issue is in the link below:
https://github.com/pluginsGLPI/formcreator/issues/2911