You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I can create a task in a ticket and assign it to somebody.
But!
If the assigment tecnition is not assign to the ticket in any role - he cannot know about that task (and see, and check/uncheck the checkbox).
Also if the tecnition is assigned to the ticket, he can not check or uncheck the ticket task that was be assignet to him in case if "Home > Administration > Profiles > Assistance > FOLLOWUPS / TASKS > Ticket tasks / UPDATE ALL" is unchecked. But if it is checked - he can also check or uncheck ticket tasks that is notassignet to him.
So please give me any reason to assign the tasks!
I've already tired to fight with the understanding of logical roads of the system.
Relevant log output
No response
Page URL
No response
Steps To reproduce
No response
Your GLPI setup information
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered:
Code of Conduct
Is there an existing issue for this?
Version
10.0.15
Bug description
I can create a task in a ticket and assign it to somebody.
But!
If the assigment tecnition is not assign to the ticket in any role - he cannot know about that task (and see, and check/uncheck the checkbox).
Also if the tecnition is assigned to the ticket, he can not check or uncheck the ticket task that was be assignet to him in case if "Home > Administration > Profiles > Assistance > FOLLOWUPS / TASKS > Ticket tasks / UPDATE ALL" is unchecked. But if it is checked - he can also check or uncheck ticket tasks that is notassignet to him.
So please give me any reason to assign the tasks!
I've already tired to fight with the understanding of logical roads of the system.
Relevant log output
No response
Page URL
No response
Steps To reproduce
No response
Your GLPI setup information
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: