@Andrew I appreciate that community threads are not the same thing as closed tickets.

My observation is that the behaviours are essentially the same. Wanting to query an historical dataset to assign attributes and then organise based on those attributes.

Nicole wants to query a dataset (community threads) > to identify an attribute (feature request that has been built) > to gain insight into a pattern (user requests against feature build)

That is what tagging gives to tickets, to assume tagging is no longer relevant after a ticket is closed is not supported by user behaviour (it has been a feature request for at least 10 years.) So I want to perform exactly the same sort of analysis that Nicole is offering, but I need to be able to retrospectively assign attributes to tickets (tag) in order to perform this analysis. This makes sense, as organisations might have questions that evolve over time (like Nicole offering this new way of querying the data) so with new questions comes the need to assign new tags.....

On further inspection it seems to me that there are a bunch of 3rd party apps that integrate with ZenDesk to offer this type of data query ...