[TICKET_STATUS_NEW => 'Open it', TICKET_STATUS_OPEN => 'It stays Open', TICKET_STATUS_RESOLVED => 'Reopen it - back to Open'][$s_id] ?? 'Move it back to Open']; if (!$s_builtin) { $s_reply_choices['0'] = 'Leave it in this status'; } foreach (ticketStatusReplyReady() ? ticketStatusReplyTargets($s_id) : [] as $target_id => $target) { if ($target_id !== TICKET_STATUS_OPEN) { $s_reply_choices["to-$target_id"] = 'Move it to ' . $target['ticket_status_name']; } } $s_reply_value = $s_reply_to && isset($s_reply_choices["to-$s_reply_to"]) ? "to-$s_reply_to" : (string) ($s_builtin ? 1 : $s_reply); ?>
Looks like
data-ticket-status-name>
ITFlow's own statuses keep their names.
Shown when the status is hovered - in the pickers, on the board and on tickets.
Fixed for ITFlow's own statuses. A ticket in a paused status never warns or breaches on resolution - the time already spent is kept, and the deadline moves out when it comes back. The response clock always runs.
A closed ticket takes no replies. By email, in the portal or by text. Move it to a status such as "Client responded" to see at a glance which tickets have a new answer; back to Open suits a status that waits on the client. Whoever it is assigned to is told either way.
An agent moving a ticket into this status before anyone has answered the client meets - or misses - the SLA's response target then: setting it by hand or in a reply, or assigning a new ticket, which moves it to Open. Once per ticket. With the email, the contact and watchers get the "ticket assigned" message from Settings > Tickets, kept on the ticket as a public note; if nobody could be emailed, it doesn't count.