What is best practice for "pinning" posts to a topic?


(Drew) #1

Often there will be a thread with 50+ posts about a newly-introduced bug on our platform and we want to let users know we are working on it. If we just add it as a normal post, it can quickly be drowned out by other replies. We can mark it as the “solution” to pin it to the OP, but this is hacking a feature to do something it wasn’t intended, and misleads users who see the solved checkmark into thinking the issue is resolved. We could alternatively edit the OP to something like:

Edit: This is being looked into by engineers
[quote]

but some users don’t like their posts being edited.

What is the ideal way to handle this?


(Stephen) #2

If users don’t have access to tagging themselves then why not have staff tag topics as acknowledged / investigation / resolved? Is it important that users see specific replies?


(Drew) #3

They have access to tagging, but even if not, tags are tucked away and hard to notice. And yes, contents of replies are important to see since they may contain information like expected resolution time, requests for more info, etc.


(Stephen) #5

I can see some value to pinning posts within topics themselves. Until someone develops the equivalent of a blue post (staff post) plugin to highlight where staff posts are in the topic/timeline and then hop between them it’s useful to know where to look for official responses.

From personal experience people bookmark the threads directly, particularly when it comes to tracking issues and bugs. They may never revisit the parent category to see other topics.

It’s a hard behavior to crack, which is why we’re forced to consider stuff like edit the initial post or abusing the Solved plugin. Neither is a real solution, but I’m not sure one exists right now?