This early access program (EAP) currently has the following limitations. We plan to address these things before the General Availability (GA) release. Keep an eye on this article to keep up to date with any changes.
- Deleting ticket statuses: You cannot delete a ticket status.
- Conditional ticket fields: Ticket statuses that you create can’t be used in conditional ticket fields.
- Support placeholders: Ticket statuses that you create can’t be used in placeholders. The existing {{ticket.status}} currently displays the status category.
- Explore integrations: New ticket statuses are available for a subset of reporting metrics in Explore. See Custom ticket status attributes in Explore.
- Contextual workspaces: Using new ticket statuses with Contextual Workspaces in not yet supported. If you use new ticket statuses in a contextual workspaces condition, then you can’t submit tickets within that workspace.
- Jira integrations: New ticket statuses are not yet available for Jira integrations.
- Keyboard shortcuts
- ZAF
Known issues
This EAP currently has the following known issues:
- The new My Requests page in Guide only displays status category and doesn’t show new ticket statuses.
- The Suspended Ticket view doesn’t display the Ticket status column correctly and misaligns other columns.
- When you disable ticket statuses from the Settings page, you must refresh the page to access the “Activate ticket statuses” button within the Ticket Statuses menu.
- It’s possible to add a second status with the same label as a default status from another status category. For example, it’s possible to add a status labeled “Open” under the “Pending” category, resulting in having two statuses with the same label, “Open - Open” and “Pending - Open”.