Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem edition field describe #15740

Closed
2 tasks done
ltfarm opened this issue Oct 9, 2023 · 1 comment
Closed
2 tasks done

Problem edition field describe #15740

ltfarm opened this issue Oct 9, 2023 · 1 comment
Labels

Comments

@ltfarm
Copy link

ltfarm commented Oct 9, 2023

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

Version

10.0.10

Bug description

Hi, how are you?

A question has been causing some internal dilemma with the areas that use GLPI, the technician can change the description of the ticket sent by the user.

By blocking ticket updates for the technician, it blocks the option to edit the ticket, but in addition, it also changes the possibility of changing fields such as category, type, and origin.

In addition, if the technician has the option to be in charge, this update option is ignored.

I believe that this is a misguided behavior of the system. Especially when non-ICT areas use the system. The human resources area dont uses it because there is a possibility that the ticket can be changed in its original description, even if this can be seen in the history, it creates a totally unnecessary dilemma.

This issue can create dilemmas of information security, gpdr, among other factors.

Relevant log output

.

Page URL

.

Steps To reproduce

No response

Your GLPI setup information

.

Anything else?

.

@github-actions
Copy link
Contributor

This issue has been closed as we only track bugs here.

You can get community support on forums or you can consider taking a subscription to get professional support.
You can also contact GLPI editor team directly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants