将帖子“置顶”到主题的最佳实践是什么?

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?

3 个赞

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?

1 个赞

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.

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?

4 个赞

Moving this to a feature request as I’ve now had the same request from a customer.

Their use case is the same as the OP.

  • A bug or feature is being worked on
  • Staff updates are being lost in the noise (even with Staff Colour)
  • They are not comfortable editing the OP to include updates
  • They don’t want to mark something solved because it’s not
6 个赞

I can see use case here and also see how it departs from “solved”

In particular you would allow multiple posts to be “featured” in the OP:

Jane "pm" 2 hours ago: We will be looking at this [v expand]
Jill "dev" 1 hour ago: I am working on a fix [v expand]

@codinghorror I wonder if this is core feature, aka “Pin post…” complete with “how long you want to pin it” or in the far to rare department and should be a discourse-pinned-posts plugin.

Personally it feels like a discourse-pinned-posts plugin to me, but it shares lots of DNA with discourse-solved so we would need to be careful about code duplication here.

6 个赞

Not exactly, maybe solved needs an in-progress state that behaves almost the same way as solved but does not confer full solved-ness.

6 个赞

Solved only works if it’s a unique post about an issue, or there’s a definitive endpoint.

It would be useful to move between staff/moderator responses in a topic regardless, or offer a tweaked summarize which includes them all.

1 个赞

One idea we came up with on my forum is to edit the topic title. Inelegant, but at least it will get the members’ attention.

1 个赞

I really like this idea – maybe “potential solution” or something like that? (In my ideal world, this would be a setting that could be enabled if an admin felt it appropriate with a little text box for the title of the “in progress” or “potential solution” or whatever.)

1 个赞

我非常好奇这个 #feature 请求最终结果如何。现在是否有办法实现这一点?如果有,在哪里可以找到该设置?

如果没有,除了编辑原作者或主题标题外,大家是否有新的建议?

能否稍作扩展,并最好提供一个论坛主题的链接,说明您希望在哪里使用此类功能。

多年来我们已进行了一些改进,现在您可以对帖子进行批注,但除非手动编辑主题帖(OP),否则仍无法自动在主题帖中突出显示多个帖子。

1 个赞

2019 年 3 月,@HAWK 发布:“由于我现在收到了来自客户的相同请求,我将此移至 #功能请求。”我只是想询问,在 Discourse 中,将帖子在主题内置顶的功能是否已作为正式功能实现。

和这个一样 @michellefs .. 听起来人们想要一个明确的“未完成,但正在进行中”的“解决方案”标记……就像“半成品解决方案”、“四分之一成品解决方案”,甚至可能是一个进度条,如果人们想要一个“完成度”的百分比估算的话?

这至少能让人们知道解决方案正在进行中,而不是根本没有被处理。

不太确定我是否正确理解了主题标题,但在我(前公司)中,我主要在三种场景下使用了“固定评论”:

  1. 对于最佳答案,类似于“解决方案”功能,我们通常只需要固定一条评论。
  2. 对于社区AMA(问我任何问题),我们为用户和员工之间的话题问答开设一个主题,我们通常需要固定至少 30 多条评论来突出员工的回复,每季度一次。
  3. 在社区活动中突出精彩的用户生成内容(UGC)(照片、视频,甚至是表情包),例如每月摄影主题,我们通常需要固定至少 10 多条评论。

希望这有帮助 :wink:

2 个赞

那不是用 Discourse 做的,对吧?
我同意,能够将任意数量的回复固定在主题第一个帖子底部(作为实际回复的链接,以避免弄乱回复线索)会很有用。