Permission to edit/complete/delete is overridden in the following cases:
- If user has project_management permission set to "Yes"
- If user is a project leader
- If user is the author of the ticket
- If a ticket has no assignees
- If user is assigned to a ticket
Probably it's one of the reasons above that allows your users with only "Can Create" permission to manage Tickets.
Thanks for the additional information. FWIW, I don't think that is intuitive at all - in our case we don't want clients to EVER be able to edit a ticket once they create it. From that point on its up to our AMs/PMs to manage the tickets. We assumed setting their permissions up to not have "manage" permissions would accomplish this.
I would also suggest that you make note of these overrides in the administrator documentation as there is currently no mention of any caveats to permissions.
I have a huge problem with this as well.
In my case - PM creates ticket, Studio Manager assigns to the relevant resource in studio and now that resource has full access to edit or delete that information.
It does not make sense.
If user is supposed to work on something, he should be albe to make appropriate changes (attach new files, change description and provide more details etc). For tickets, all changes to a specific ticket are saved, so there's no questions who changed what and when.
This is by design and not likely to change any time soon.
So why can these users still edit and complete tickets?