Customize Status Field Values

Finally!

Excited to see how this feature will be implemented.

Hello Everyone,

I understand that customizing ticket statuses has been a long outstanding requirement. I can confirm that Zendesk has this feature scheduled in our product enhancement pipeline. This community thread has been very helpful and I would appreciate if we get more feedback on our proposed solution and its impact on other Zendesk features that we have built over the years. I will be sharing a research study sign up link soon for customers who would like to collaborate with us in building a solution. I will keep this community updated on our plan and progress.

Thanks!

Gaurav Parbat

Product Manager, Ticketing

Anders Juul Jensen

That's not how it works around here. The feature request has to be 10+ years old first. ;)

-----------------------------------------------

All joking aside I do not believe this is likely to be implemented any time soon.

Therefore, I have gone through the process of manually adjusting some of the current statuses to get an effective extra status or two. That is one of the User Tips and Tricks I am planning on writing up. I will post it here once I have finished it. 

I have separated the "Pending" Status into 2 effectively different statuses. The first is where the "Pending" Status repeatedly pokes the customer for a response and the second is where it matches the first but also closes the ticket if they do not respond after 7 days.

I have also separated the "Solved" Status. This allows us to set a status of solved but the ticket will reopen at a future date. 

------------------------------------------------

I am providing a link to the User Tips I have written and the ones to come for those that would like to follow the post in the meantime. 

https://support.zendesk.com/hc/en-us/community/posts/360044286213-Ranking-Tips-to-be-written-up

i'm like... whaaat?

we've just moved from Happyfox to Zendesk because our It-service desk is expanding.
To our horror we find, that simple custom status settings aren't availeble??

Must say i'm quite dissapointed already ...  :-(

DEFINITLY an upvote for this ... and yes people have been asking for minimum 3 years for this...
politly said, get your fingers out and start programming ...

Hi, we have developed that free app that won't solve the issue but at least minimize the impact :

https://www.zendesk.com/apps/support/advanced-workflow/?source=app_directory

It add a custom fiields with sub status. 

This is still a very much wanted feature.

We have been using Zendesk as an internal ticket platform for years, but we are considering moving elsewhere once we start using Zendesk for our external support since this feature is yet to be implemented.

Configuration of Status "Pending" and "On-hold" need to be visible to end-users (clients)

Make client-facing statuses editable so we can decide what wording displays to them.

If it is transparent and shows Closed they know they need to create a new request as that one cannot be reopened.  

Also, changing New to Awaiting Agent engagement instead of Open and adding Outsourced for Awaiting Third Party.

I honestly can't believe this is still a thing we have to request, but here's my +1 to throw on the fire.

Hello all

Whaoo ! A request open 10 years ago, 93 comments, and the answer I got when I open the same question is " it's technically a very heavy lift and therefore difficult to prioritize". Honestly 10 years ago other tools were already doing it; This is a major pain for our projects. See you in 10 years on thsi one again !

Thanks all contributors for pushing on this one.

+1.

I understand that a lot of the logic processes are based around this field, But this has been requested for such a long time that I would have liked to see it looked at sooner. Heres hoping it is available soon.

We want to be able to have an Escalated status (or several). This need has come from a client who wants more clarity around what is happening with the issue. This would be reportable and visible to the end-user through the portal. It's this last need that necessitates using a status.