For the fourth time since implementing “Unhandled” one of our staff has deleted the “Unhandled” tag.
This isn’t the end of the world, but it does essentially handle things that haven’t been handled yet, making it so some customers do not get replies.
When users click a tag, they’re taken to a list of all the posts with that tag (good).
When they click the “Delete Tag” button they get a warning (good):
But the warning isn’t explicit about what is about to happen. If the user is thinking “I want to remove this tag from this topic” then the warning fits with that mental model, and OK seems like a perfectly good answer.
But if the warning said “Are you sure you want to delete this tag and remove it from all 675 topics it is assigned to?” then the user would likely not click “OK”.
I suggest this as an alternative to what I imagine is much harder: making the “unhandled” tag immune to deletion.
Even without the count of topics, simply rewording it to say “This will delete the tag from all topics to which it is assigned.” may save us considerable headache.
We’ve lost our unhandled state four times the “unhandled” system was rolled out for McNeel - I’d really appreciate it if we could work toward avoiding this again. I believe we’ve paid for some unused dev hours on the tagging/assignment project. Can we get this done sooner than later, please?
