- When a New ticket is assigned to an agent, the ticket status automatically changes to
Open. You'll see the change after you update the ticket.
If you’ve activated ticket statuses: The ticket status automatically change to your default ticket status in the Open category.
- After a ticket's status has been changed from New, it can never be set back to New.
If an end user comments on a ticket with a status set to Pending, Solved, or On-hold, the ticket status is changed to Open.
If you've activated ticket statuses, when an end user comments on a ticket with a status in the Pending, Solved, or On-hold status categories, the ticket status is changed to your default ticket status in the Open category.
- A ticket's status can't be set to Solved by an end user or agent without an assignee. If an agent submits a ticket as Solved and there is no assignee, the system automatically makes the agent who solved the ticket the assignee.
- Ticket type field values aren't editable.
- When you set a priority, you can't reset it back to no priority. You can always change it to a different priority.
- Tickets with a status set to Closed can't be updated, but they can be deleted. Requesters can create a follow-up request that references a closed ticket, but they can't reopen the closed ticket.
- When a ticket has been assigned to a group, an admin can reset it to no group by creating a trigger or automation setting the group value to null.
- If there's only one group, all tickets are automatically assigned to that group.
- If there is only one agent in a group that can be assigned tickets, all tickets assigned to that group will automatically be assigned to that one agent. Some agents in groups, such as light agents, do not have permission to be assigned tickets.
- If there's only one agent in an account, then all tickets are automatically assigned to that agent and the agent's default group.
- If an agent is only allowed to view tickets within their groups, and then they forward an email to Support, a new ticket is created and automatically assigned to the agent's default group. For information about how your account's default group and an agent's default group affect ticket assignment, see Changing the default group for your account or an agent.
- You can't assign a ticket to an agent without first assigning it to a group.
- If an agent takes or automatically solves a ticket without assigning it to a group in the process, the ticket is assigned to the agent's default group.
- Tickets are automatically closed 28 days after they're set to Solved, regardless of any triggers or automations.
- The requester field is mandatory. By default, Zendesk populates it with the person who created the ticket. If your agents are creating tickets on behalf of end users, and the agent forgets to add a requester, the agent becomes the requester.
- If CCs and followers are enabled and an agent replies to a ticket notification they are no longer the requester or assignee for, they are automatically added as a follower to that ticket.