Closed VanAxl closed 2 years ago
The actor fields seem to take into account the current user's active entities for the results. If your technicians are currently in the Root Entity and are not including sub-entities (The entity in the top right will show "Tree structure" at the end of the name), it will not include users in sub-entities.
The actor fields seem to take into account the current user's active entities for the results. If your technicians are currently in the Root Entity and are not including sub-entities (The entity in the top right will show "Tree structure" at the end of the name), it will not include users in sub-entities.
For the test I made, I confirm that the "active entity" was the Root entity, including all sub-entities (Tree Structure is written on top right of the page). So I should get all users available as Actors, right ? But I can only add / select Users linked to Root Entity. If I manually change the ticket to another entity (i.e. Root > Entity1 ) I can now select all users from the Entity1, even if the current active entity remains unchanged.
The same thing happens to me, you have to change the case to the entity of the requesting user and I don't always remember which entity it belongs to, that didn't happen in version 9.x, you could choose any user in the sub-entities in glpi 10.0, you only assign a user from the current entity even if it has the tree structure activated for the sub entities.
I hope that will be corrected in the next release ... to have back the possibility to set any requester from the sub tree.
Some technicians tell me that it is very cumbersome to enter user tickets, so I check in previous versions of glpi and apparently the problem arises with the fact of joining groups and users in the same entry, in previous versions of glpi It only allowed to place a requester when creating the ticket and it was automatically moved to the entity of the requesting user and it seems to me that it is the best behavior because 99% of the cases belong to a single user but what happens when they have more than one user out of two different sub entities to where the ticket is moved, only one user would have privileges to see the ticket unless the tickets have the option to be visible to the sub entities and remain in the parent entity
Code of Conduct
Is there an existing issue for this?
Version
GLPI 10
Bug description
On previous GLPI version (9.5.x) when a user called us directly by phone, the technician quite often uses the create ticket interface to declare the incident for that user. We filled the new ticket with all information, and we set the requester to be the user on the phone. On the GLPI 10 test platform, we have no easy to change the requester while creating get new ticket, it seems to be set by default to the current technician logged. and we have on the right of the creation form the "Actor", but it seems to not display all sub users of the current entity. So the technician need to open back the ticket, after it has been created, to change its entity, and then to be able to select the good requester. Is it a bug ?
Many thanks. BR, Nicolas
Relevant log output
No response
Page URL
No response
Steps To reproduce
create new ticket, try to change the requester to any users member of a sub entity.
Your GLPI setup information
Information about system installation and configuration
Server
GLPI constants
Libraries
LDAP directories
SQL replicas
Notifications
Plugins list
Anything else?
No response