Add reason for rejection of a post

for the first posts of a user, which may need to be approved (based on a forum policy), a reason for rejection may be good.

when an admin reject a “waiting for approval” post, it’d be good (educational for users) to add the reason so that this reason goes to the user directly.

currently we message users about the reason their post is not accepted. it’s a bit of work, as in a message you need to say hi and bye :wink: .

I’m not sure if this can work, but when admins click on reject button, a window like the flag window can open and admins can write the reason or choose among the list:

31 个赞

Are there any developments?

1 个赞

I have been against unconditionally notifying users here of rejections. (we now unconditionally notify on approval)

But… strategically if the moderator opts to give a rejection reason, I am all for reducing moderator friction.

I would like the full picture here, what are some examples of reasons why you would reject first post?

cc @eviltrout

7 个赞

I guess anything that causes one to flag a post, can cause rejection of the first post as well! e.g.:

  • duplicate of another thread

  • non-relevant, advertisement, spam, … ; or let’s say out of the community scope (according to the “community guidelines”)

  • very poor writing or non-clear message (bad spelling, bad grammar, …) such that moderators can’t edit it easily

5 个赞

I am also running into this same issue, and would love this feature!

2 个赞

In my case, new members must submit one high-quality submission before they are given full access to the community. Thus, it would be really great to give them some feedback on their submission if it wasn’t accepted, as to encourage them to try again. Alternatively, if their submission is good but we have some edits, we would like to share some comments on how to improve the post before officially accepting it.

5 个赞

With premoderation of new users/topics this is highly valuable as it’s often the first interaction with the community. And if someone tries to post and just gets a rejection it’s likely that they’ll never come back. The most common case for us is that we need to redirect them from our discourse based discussion forum to our Q&A website.

To that end we have a policy of the following:

  • Create a message to the user with subject "Re:
  • Tell them the reason for the rejection (copy and paste reasons stored in our moderation guidelines for convenience)
  • Copy their content into the bottom of the message so that they have a copy of their question that they might have spent non-trivial time to create.
  • Send the message
  • Then reject their post

The benefits of this workflow are that the user gets a reason and can be nudged in the appropriate direction. If we’re already reviewing it knowing the reason makes sense.

In addition we added the copy and pasting of the content because when the post is rejected it’s no longer viewable. And if it’s a good question but misdirected or something else that needs editing and with some iteration would be valuable content, it’s frustrating for the users to lose access to it when we reject the post.

5 个赞

This would be a feature we would love to have as well.

Are there any plans to implement it any time soon?

3 个赞

I keep hitting this issue on my forum. It would be nice to have the same kind of options that are available with flagging when rejecting new posts, as each time I reject I have to manually go message the user to inform them why I’m rejecting.

4 个赞

We are also looking for this feature, if the team can pull this off will be great help, our community is very large, need this rejection thing to manage everything, rightnow we have to manually PM every user regarding post rejection. :neutral_face:

4 个赞

这是我们需要的功能。我们使用审批机制来处理漏洞报告(在拥有超过15万用户的情况下,用户往往倾向于先发帖后阅读)。我们有一个通用的“支持”论坛,鼓励用户在那里提出“如何使用”类的问题。如果出现问题,我们会要求他们在“漏洞报告”板块发帖。问题在于,如果他们的帖子被拒绝(例如作为重复帖子或因缺乏适当信息等原因),他们却无从得知……帖子直接消失,他们甚至不知道帖子是否成功提交。

这导致他们倾向于在摩擦更低的“支持”论坛发布漏洞报告,内容往往完全相同,且缺少我们需要的、用于复现问题的关键信息。这给我们带来了更多的工作量。我希望能够以具体理由拒绝帖子,从而教育用户如何正确提交漏洞报告,或者链接到已有的相关报告。

以下是用户将此作为顾虑提出的逻辑流程:

目前“漏洞报告”板块的帖子运作方式下,你可能永远看不到任何明确表明帖子已被接收的反馈。此类帖子需要版主审批后才能显示——这很有道理。一个漏洞可能影响许多人,如果没有审批机制,可能会产生许多不同的讨论线程。此外,这本身可能并非真正的漏洞。如果“漏洞报告”板块旨在同时作为漏洞列表,这也是帖子需要审批的另一个原因。

然而,如果帖子最终没有显示,似乎没有任何明确的确认表明帖子已被接收。即使(或类似的报告)最终显示,也可能需要相当长的时间。如果问题持续存在,你可能会想:“帖子真的被接收了吗?我应该再发一次吗?”你也会花费时间检查是否有任何新内容出现。

这令人沮丧。

但如果作为“建议与反馈”发布,帖子至少会显示出来,这样你就能看到它已被接收。即使后来被移动或删除,你至少知道它没有在传输过程中丢失。

这就不那么令人沮丧了。

从试图通过引起关注来提供帮助的用户角度来看,因此在“建议与反馈”中发帖似乎比在“漏洞报告”中发帖更有效。在“漏洞报告”中发帖,你还必须至少提供一个标签,这也阻碍了用户在那里发帖。而且,系统要求你提供大量可能并不相关的信息。

实际上,论坛的行为机制鼓励我们将问题作为“建议与反馈”而非“漏洞报告”来提交。

有人可能会争辩说,这可能会产生审批机制本意要避免的重复线程。然而,我们本就应该在发帖前查找现有线程,而且等待片刻让其他帖子有机会显示也是轻而易举的。

因此,综合来看,从希望提交报告的用户角度来看,在“建议与反馈”中发帖似乎仍然更有效。

8 个赞

我们昨天就需要这个功能。我每天会拒绝大量新主题,因为它们与现有主题重复,但那些用户却连一条解释被拒原因的消息都收不到。

我没有时间:

  • 通过私信与他们沟通并处理随后的讨论
  • 先批准主题,再立即将其隐藏并锁定
  • 先批准主题,然后打开它并将其标记为重复

当我拒绝时,我希望能够当场提供理由并立即完成操作。这可以是一个标准理由(重复、超出社区范围、写作质量差、内容不当),并可选择附带一条简短说明。

缺乏这一功能让新论坛用户感到非常沮丧。

4 个赞

我同意。如果你拒绝了一篇帖子或主题,但没有向该用户显示任何内容且未提供解释,除非你稍后给他们发送私信,否则这会留下不良印象。我非常希望这一功能能够被实现。此外,从审核队列跳转到用户个人资料再发送私信非常耗时。如果所有这些操作都能在一个地方完成,将会方便许多。

1 个赞

这不已经在发布列表里了吗?

看看 #releases……哦等等,不对,那是用于拒绝 账户 的,我搞错了。

2 个赞

没错,希望评论功能也能有类似的设计。

2 个赞

我也希望有这个功能。

我习惯使用 Mailman 2,其中有一个“拒绝原因”的文本框,所以很惊讶被拒绝的邮件这么快就消失得无影无踪!

(好吧,它并没有消失得无影无踪——我可以在管理员操作日志中看到它。)

1 个赞

由于 @TheBaby5Marketplace 中的请求,我再次提出此问题。

我认为至少需要在使用者的帖子被拒绝时通知他们。目前,用户对此一无所知。

目前的审核批准流程如下:

  1. 用户在受监管的类别中发帖
  2. 发布后,用户会看到 js.review.approval.description(只是一个弹窗,没有工作人员的消息)
  3. 如果帖子被拒绝,用户不会收到任何通知。

我认为基本功能应该是发送一条帖子已被拒绝的消息(可能来自工作人员)。我不需要具体的理由——例如,我们可以编辑 js.review.approval.rejected.message 并在那里添加最常见的原因。这只是一个想法。

原始市场帖子在此

4 个赞

我同意这一点,但前提是针对合法用户,并且希望告知他们帖子被拒绝的原因。

然而,如果是垃圾邮件发送者,我认为不发送通知是合理的。您不希望通知垃圾邮件发送者他们的帖子已被拒绝(删除),从而导致他们再次尝试。:slightly_smiling_face:

垃圾邮件原因不应发送通知。对于其他原因,则应该发送。

2 个赞

如果团队希望构建所请求的功能,以下是待审核帖子(已审核类别)的当前选项。

针对垃圾邮件,我们可以直接删除用户。对于拒绝情况,我们可以采用我在上一帖中建议的简单方案。这是团队最便捷的快速解决方案。假设团队对完整请求没有兴趣,并且已有相关的 Marketplace 主题开放讨论,此外,本主题发布于 2020 年……:thinking:

1 个赞

Mailman 2 中的对应选项是“拒绝”(可选择提供理由)和“丢弃”(完全不发送通知),此外还有“延迟”(稍后决定)和“接受”。

此外还有“丢弃所有标记为延迟的消息”的选项。默认状态是“延迟”,因此一旦您已接受或拒绝了真正的邮件,页面上剩余的内容很可能全是您希望一次性丢弃的垃圾邮件。

除此之外还有其他细节,但以上是直接可比的选项。

4 个赞