I am not entirely sure if I understand your problem correctly, please apologize if this should be the case.
So you would like to be able to add tags within the overview page itself, because this way you could categorize content more efficiently? This is not a common use case, simply because it can be hard to define which tag a topic should receive simply based of a topic title. I am wondering for which purpose in your workflow you want to use this tags for. I understand it helps you and your colleagues to find back content more easily, but I am not sure about the context of the people working with this content. Do you have specialists per product, or is this to assign topics to support representatives?
A “next” button on the topic moderation page could indeed make sense. I actually had to double check because I believe I saw something like this before. It might have been only a visual mock up or an idea...
What I think currently stands in the way of such a functionality, at least with my limited knowledge of the platform infrastructure, is that the topic moderation page does not know which filters you have applied in the overview page - it does not have this context. So, if you would have filtered in the overview on a certain tag, the topic page could not know which topic would be the next topic that you would expect to see.
Hey @Julian, thank you for your thoughts!
The idea behind tagging was for us to reorganise our content; for example, if you have a list of topics under a “report problems” section for a product, being able to tag them all as “product report problems” and move them in bulk to a new section/forum/category, or even choose to close them all off. (I also noticed that we can’t filter using the public tags at all on the Overview page, which I can only guess is also why the first options isn’t available either.)
The NEXT button for topics would’ve been of huge help especially if it at least was present if we didn’t have any filters set, so I can at the least scour through some topics than none at all.
The requirement was more of being able to manage our topics from the list page than go within, when certain actions need only be done from a larger view (close topics, mark as read, etc.)