Can I edit closed tickets?

Return to top

16 Comments

  • Rich Shupe

    This is critical to us as a Zendesk customer.

    3
  • Gatis Bertmanis

    Yeah, need to enable closed ticket editing, for the most reasonable, to unassign from assignee old tickets.

    Second, cases rises when the agent can not see other agent tickets in profile view, because there are more than 24'000 tickets, and then it shows "There are no tickets in this view". And it is caused by this huge amount of tickets, and the system can not proceed with it or takes a lot of time to load all tickets.

    Another solution would be, to allow to make a ticket filter in profile ticket view, to shows by default only, for example, last 6 month tickets, not a full load of all tickets.

    1
  • Rich Shupe

    Editing tags... there are many reasons.

    I can't speak definitively yet, because we're still evaluating the replacement software we'll be moving to, but I'm not sure if many/any others have this limitation. JIRA doesn't, for example, which I mention simply because we use that internally.

    2
  • Justyna Pultowicz

    Here also requested: https://support.zendesk.com/hc/en-us/community/posts/360034870553-Feature-Request-Ability-to-edit-closed-tickets

    I put in another usecase to why this is a feature needed. I can go out of my way to make what I want work, but it feels like there should be an easier way of doing this...

    1
  • Scott T

    There are multiple threads related to the inability to edit closed tickets and I've read most, if not all of them. One thing I have not found is the reason why this change hasn't been implemented. Many of the justifications provided by customers are deal-breakers. There are many things I like about Zendesk but, based on this shortcoming alone, I would not recommend it.

    My guess is that closed tickets are set to read-only in the database for performance reasons. Is my guess correct or is there something else?

    0
  • Nazir Kabbani

    Workaround? create a automation the opens then solves tickets every 20 days so they never stay solved for 28 days until the cut off of your choosing (repeat 20 days automation many times?)

    1
  • Nadeem Taj

    i honestly dont know why these simple requests that are so easy to implement are ignored, year after year, after year. Everyone of your customers are saying the same thing.

    Simple workaround, use another platform apart from Zendesk. I'm finding it difficult to justify the expense on a "less than adequate" platform.

    0
  • Dawie Otto

    It would be super helpful to have this feature.

    We add billing references to our tickets and sometimes we can only generate the invoice once the job is completed and signed off by the client.

    By then the ticket is already closed and we are unable to add the billing reference.

    Leaving the tickets in a Solved status for a longer period is not an option.

    0
  • Danny B.

    I used to have this understanding that we would need to update a ticket even if it is close (same use cases as above), but with some realizations, a "close" ticket is a close ticket, you should never touch those, once you opened it again or even just an update to a field, becomes an Auditing nightmare!!!

    What are team did is fine tune some process management, update what you need to update i.e. fields, comments, etc, before setting the ticket status to "solve". You can even add your own "internal status" as a custom field. Then configure an automation that if the ticket status is "Solved", and no updates to the ticket for 'x' no. days, then set to close.

    Else, you will never have an end state to your ticket lifecycle.

    0
  • Rich Shupe

    Thanks for adding your experience, that may help others. 

    However, for many ZD users this is a needed feature and is common/expected in many competing systems. Even if you can manage to make your ticket perfect before closing (which isn't always the case, is subject to human error, etc.) there are still reasons that older tickets must be changed, some of which have been listed in this thread, I think. 

    This is mandatory for us and is one of a few reasons that we're looking for another system.

    0
  • Danny B.

    Thank Rich Shupe. I totally understand where you are coming from. 

    Just from an auditing perspective, which we experienced, once you allow anyone to update a "closed ticket", you are opening it to a whole new complexities, regardless what ticketing system you used.

    Another option is to create a 'child-like' ticket that is related to a the "closed ticket". You can have a new custom field i.e. "closed linked ticket id" so you'd be able add new information (i.e. tags, internal notes, etc,) and still be able to search, report on these tickets accordingly. 

    0
  • Stephen Fleming

    As mentioned in another thread - the inability to modify information on Closed tickets is becoming very difficult.

    In particular, the inability to redact data - we would like to be able to remove certain personal data / attachments from legacy tickets for privacy compliance reasons.

    0
  • Charlie

    This is really bad. I recently made some changes to our default ticket form that hide certain fields based on a new boolean ticket field. Because the new ticket field was only recently added, and defaulted to False for all closed tickets, a ton of information was automatically hidden on these old tickets. I tried to update the new boolean field on all of those old tickets via an api script and can't? Do I have to reverse the changes we made to our ticket form to expose those fields?? Really, really bad.

    0
  • Rich Shupe

    Yes, there are many upset customers due to this. We're switching systems because of this issue.

    Worse, there's never been any justification--that I could find (and that's important for me to say)--for why it works this way or why customer needs are being ignored.

    0
  • Charlie

    It's worth pointing out too that there's problematic inconsistency in the way the logic of this behavior is applied.

    Changes made to a ticket form are reflected on closed tickets. As a result, those closed tickets -- from a UI perspective -- do not look like they did when they were closed, if the form has been changed. The ostensible intention to freeze tickets in the exact state they were in when they were closed is therefore not being achieved. 

    2
  • Stephen Fleming

    +1 for Charlie's comment.

    It's extremely frustrating when a change is to a Form and it applies to long closed tickets. What is the point of restricting users ability to modify the Closed tickets, when they can inadvertently be changed by a workflow update.

    1

Please sign in to leave a comment.

Powered by Zendesk