Mounika Sanikommu

Zendesk 很高兴宣布正式推出基于表格的自定义工单状态功能。对于基于表格的工单状态，您可以定义在某些工单表格中显示哪些工单状态。

此公告包括以下主题：

• 有什么变化？
• Zendesk 为何作出这项更改？
• 我需要做些什么？

有什么变化？

我们将通过引入基于表格的自定义工单状态来扩展自定义工单状态的功能。

管理员现在可以定义某些工单表格中应显示哪些工单状态。当您将工单状态关联到表格后，它们将在使用时自动应用于指定的表格。

基于表格的工单状态允许您根据特定的背景信息或查询类型定制工单处理工作流程，从而提高灵活性，确保专员获得最相关的状态。专员只能看到与其正在处理的工单表格相关的状态。

例如，如果您有一个“错误报告”的工单表格，您可以定义“正在调查”或“等待修复”等自定义状态。当专员选择关联表格时，这些状态将自动可用。

Zendesk 为何作出这项更改？

我们作出这项更改是为了回应用户反馈，即缺乏基于表格的动态工单状态给专员带来了挑战。专员经常需要在不相关的工单状态中浏览，或手动选择合适的选项，这不仅减慢了工单处理速度，还增加了出错的可能性。

通过此更改，您现在可以灵活自定义哪些工单状态与特定表格关联。这可确保专员仅在正确的背景信息中看到最相关的状态，并最终为日益多样化和复杂的支持工作流程提供支持。

我需要做些什么？

此功能自动可用。请参阅关于表格工单状态，了解更多信息。

如果您对此公告有任何反馈或疑问，请访问我们的社区论坛，我们将在这里收集和管理客户对产品的反馈。如需获取关于 Zendesk 产品的常规帮助，请联系 Zendesk 客户支持。

We're excited to announce the expansion of our beta program for form-based custom ticket statuses! Due to the positive feedback and success we've seen so far, we're extending this feature to a select group of additional customers.

This enhancement allows you to tailor ticket statuses to better fit your workflow, providing more flexibility and improving overall efficiency. If you're interested in participating in this expanded beta, please fill out this form. Your feedback is invaluable in helping us refine and perfect this feature before its general release.

Thank you for your continued support and collaboration!

We are writing to inform you about an important update to the Form Ticket Statuses Beta feature. These changes are designed to improve your experience and streamline your workflows. We appreciate your participation in the beta and your valuable feedback, which has guided us in enhancing the experience. Please read the following information carefully to understand the changes and any actions required on your part.

Previous Behavior:

• Previously, forms with no statuses associated would show all statuses in the Ticket UI, but this proved confusing and restrictive based on your feedback.

New Behavior:

• We executed a one-time conversion for any forms that had no custom statuses selected (and therefore all statuses selected) in order to maintain your current functionality.
• We will create associations for all default statuses only for forms with no existing associations.
• Default statuses will always be selected on all forms.
• When a new custom status is created, it will not be added to any existing forms and must be configured on each form.
• We are currently working on an enhancement to the custom status creation workflow that allows you to associate a new status to all desired forms.
• The status picker will now show only default statuses for forms with no associations.
• Existing associations will remain unchanged.

What You Need to Do:

• Update Form Statuses: Please review and update your form status associations as needed to ensure they reflect your desired configurations.

When will the enhancement be available:

• The enhancement is scheduled to be available by the end of next week.

 As always if you have any questions or concerns please post them in this community, your feedback has already been invaluable in improving this beta and I really appreciate everyone that has chimed in thus far.

Hey everyone, thank you for taking the time to provide us with this feedback. We apologize for the delay on our end in providing you with a response to your feature request.

This is a great feature request and I have added it to the backlog for future consideration. This means that we will think about adding it as a priority later in our planning cycle. We are going to leave this post open for comment to allow others to provide their feedback and use cases, however please note as is stated in our Community Guidelines that we can not commit to prioritizing any one piece of feedback we receive in the community. 

Hey everyone, thank you for taking the time to provide us with this feedback. We apologize for the delay on our end in providing you with a response to your feature request.

This is a great feature request and I have added it to the backlog for future consideration. This means that we will think about adding it as a priority later in our planning cycle. We are going to leave this post open for comment to allow others to provide their feedback and use cases, however please note as is stated in our Community Guidelines that we can not commit to prioritizing any one piece of feedback we receive in the community. 

Hey everyone, thank you for taking the time to provide us with this feedback. We apologize for the delay on our end in providing you with a response to your feature request.

This is a great feature request and I have added it to the backlog for future consideration. This means that we will think about adding it as a priority later in our planning cycle. We are going to leave this post open for comment to allow others to provide their feedback and use cases, however please note as is stated in our Community Guidelines that we can not commit to prioritizing any one piece of feedback we receive in the community. 

Hey Brandon, thank you for taking the time to provide us with this feedback. We apologize for the delay on our end in providing you with a response to your feature request.

We wanted to let you know that at this time we are not able to commit to building this feature. We understand this may be frustrating but wanted to ensure we closed this loop to remain transparent.

Hey everyone, thank you for taking the time to provide us with this feedback. We apologize for the delay on our end in providing you with a response to your feature request.

This is great feedback and I have added it to the backlog for future consideration. This means that we will think about adding it as a priority later in our planning cycle. We are going to leave this post open for comment to allow others to provide their feedback and use cases, however please note as is stated in our Community Guidelines that we can not commit to prioritizing any one piece of feedback we receive in the community. 

Hey CJ Johnson, thank you for taking the time to provide us with this feedback. We apologize for the delay on our end in providing you with a response to your feature request.

We wanted to let you know that at this time we are not able to commit to building this feature. We understand this may be frustrating but wanted to ensure we closed this loop to remain transparent.

Thank you all for taking the time to provide us with this feedback. We apologize for the delay on our end in providing you with a response to your feature request.

This is a great feature request and I have added it to the backlog for future consideration. This means that we will think about adding it as a priority later in our planning cycle. We are going to leave this post open for comment to allow others to provide their feedback and use cases, however please note as is stated in our Community Guidelines that we can not commit to prioritizing any one piece of feedback we receive in the community.