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 with hide ticket not assigned #3843
Comments
Another bug: The user who can only see the conversations assigned to him, cannot start conversations, always gets the error: "Not enough permissions" |
Fixed in the |
Hi, thank you very much! I also discovered a way to circumvent the system if the user only has permission to view his tickets. The user just needs to go to notifications, tick "Notify me when There is a new conversation", and he will receive an email for each conversation created by everyone. Maybe this can be solved by simply creating a way to block notification editing permissions, it could be done that only administrators can set notifications for users, I don't know, I'm also waiting for your reflection on the matter. |
I have tested the changes, the draft problem has been resolved, but the user is still not able to start conversations, the "Not Enought Permissions" error always comes up. But I don't think there are any further permits to be granted. |
…ly for assigned to him conversations - closes #3843
It should be fixed now in the |
Thank you! |
After applying this FIX, normal users, without ticket viewing limitations, when they try to access a conversation not assigned to them, receive the "Access Denied" error, they see them, but when they try to access it says that it is denied. I did some tests and it seems that the problem is caused by this change: 911e157#diff-b1934e93868d34dd182708708bf54321fabc4eb34139c5783f81120a30b463e9 |
It should be fixed now. |
Thank you! |
Hi,
I was looking for a way to hide Tickets not assigned to that user, I found this: #701
It works well, however there is a problem, if the user starts creating a draft and then exits to resume it later, the user will be unable to resume the draft even if created by him.
The text was updated successfully, but these errors were encountered: