shd_assign()

shd_assign() 

Sets up the assignment UI and invokes the template.

This validates that the user can see the ticket in question initially, before determining the level of assignment that can be carried out.

Users who can assign any ticket cause a query to trigger to identify users who have shd_staff permission (and thus can be the target of assignment) and the template is loaded with a dropdown to provide this choice to the user.

Users who can only assign to themselves will at this point have the ticket assigned to them if it was unassigned before, or unassigned from them if they are able to assign tickets to themselves in the first place; if it was assigned to someone else, they will not have the option.

Access through action=helpdesk;sa=assign;ticket=x;sessvar=sessid before redirecting back to the ticket, or add ;home to the URL to have it redirect back to the home page (passed through to the form for shd_assign2()'s use too)

shd_assign2()

shd_assign2() 

Handles the actual assignment form, validates it and carries it out.

Primarily this is just about receiving the form, making the same checks that shd_assign() does and then logging the action before passing over to shd_commit_assignment() to actually assign the ticket.

shd_commit_assignment()

shd_commit_assignment(integer  $ticket, integer  $assignment,   $is_ajax = false) 

Actually commits a ticket assignment to the database.

This function sets up the relevant options before handing over to shd_modify_ticket_post() which is the preferred way to modify tickets generally. No permissions check is performed here.

Relies on $context['shd_return_to'] to have been set, defaults to 'ticket' to return to ticket, otherwise return to home page on value of 'home'.

Parameters

shd_get_possible_assignees()

shd_get_possible_assignees(boolean  $private = false, integer  $ticket_owner, integer  $dept = -1) : array

Return a list of possible users that can be assigned a ticket.

This function centralises who a ticket can be assigned to. Currently this is:

• user with shd_staff permission
• can see "any" ticket (not just their own)
• additionally, if the ticket is private, the user must also be able to see 'any' private ticket.
• additionally, check whether user is staff + ticket starter, and then whether we should block them from being assigned
• (since 1.1) additionally if we have set the option, which users are true admins, and if so, remove them from the list too

Parameters

Returns

An indexed array of member ids that this ticket could be assigned to.