Closing of threads
I guess it depends on how you want to use zendesk, but I feel like it could benefit from not closing topics as aggressively. Case in point: the feature request that wanted clicked suggestions to be tracked. The response was this would take too much space on the server, and the topic was closed. Had it not been closed, I would have suggested there to use a client side mechanism, like local storage or indexedDB. Heck, even old CSS visited might work. Of course there might be reasons why that isn't a workable approach either, but my main point is that the topic was closed, so there couldn't be a discussion on if that would be helpful.
-
Official comment
Hi there!
We indeed close them for the reasons @Sad mentioned, but let's get it opened again, all feedback and ideas are welcomed! :)
Reopened:
Comment actions -
That's a common way to do it in development so wouldn't blame them ..You review and if it's not coming up, comment and close it. Helps keeping things tidy and manageable. You just can't have them open left and right. Difficult to track and leads easily to non answered messages as they go unnoticed which leads to angry comments about being ignored, been there =D
-
I've been involved in several software projects, so that's why I phrased it as I did. There are pros and cons with closing topics, but we had best success when we allowed people to respond for a while even after we had made a decision. Sometimes people added information that made us change our minds. Sometimes people were disappointed and vented, and it was better to have that in that thread than elsewhere. :)
Please sign in to leave a comment.
Comments
3 comments