Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 7CBBC200B49 for ; Wed, 3 Aug 2016 17:10:30 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 7B519160A5D; Wed, 3 Aug 2016 15:10:30 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id C0EBB160A86 for ; Wed, 3 Aug 2016 17:10:29 +0200 (CEST) Received: (qmail 4527 invoked by uid 500); 3 Aug 2016 15:10:29 -0000 Mailing-List: contact dev-help@allura.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@allura.apache.org Delivered-To: mailing list dev@allura.apache.org Received: (qmail 4427 invoked by uid 99); 3 Aug 2016 15:10:28 -0000 Received: from allura-vm.apache.org (HELO allura-vm) (140.211.11.147) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Aug 2016 15:10:28 +0000 Received: from allura-vm.apache.org (localhost [127.0.0.1]) by allura-vm (Postfix) with ESMTPS id 84842280253 for ; Wed, 3 Aug 2016 15:10:28 +0000 (UTC) Content-Type: multipart/related; boundary="===============3548239380783845807==" MIME-Version: 1.0 To: dev@allura.apache.org From: "Dave Brondsema" Reply-To: "[allura:tickets] " <4900@tickets.allura.p.forge-allura.apache.org> Subject: [allura:tickets] Ticket 4900 discussion Message-ID:

Sender: tickets@allura.p.forge-allura.apache.org In-Reply-To: <5451bebd6d19cd63b88e142c.tickets@allura.p.forge-allura.apache.org> References: <5451bebd6d19cd63b88e142c.tickets@allura.p.forge-allura.apache.org> Date: Wed, 3 Aug 2016 15:10:28 +0000 (UTC) archived-at: Wed, 03 Aug 2016 15:10:30 -0000 --===============3548239380783845807== Content-Type: multipart/alternative; boundary="===============2431221064463181914==" MIME-Version: 1.0 --===============2431221064463181914== MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit - **status**: open --> closed - **Comment**: Fixed in [#8110] --- ** [tickets:#4900] comment moderation UI needs work [ss488]** **Status:** closed **Milestone:** unreleased **Labels:** support p3 moderation ux **Created:** Tue Sep 11, 2012 03:18 PM UTC by Chris Tsai **Last Updated:** Fri Dec 05, 2014 04:48 AM UTC **Owner:** nobody [forge:site-support:#488] >the sf 2.0 moderation queue lacks links to the tickets. this makes it quite hard to use, as the tiny diff for each moderation entry sometimes doesnt seem to contain the relevant spam. >additionally, some moderation items just say (no subject) for some reason i dont understand--so i dont even know what ticket they are for. >the moderation queue needs to always link to the ticket in question. >finally, in the ticket thread itself, if i see "post awaiting moderation", i should also see the comment in question, marked as pending moderation somehow. if i am in a thread and i see something that needs moderation, but have no way of knowing what the content is, i can't moderate it. am i supposed to go to the moderation queue and hunt through it for the ticket number? I guess I have to, because thats where the button would be to junk it. >This interface is quite cumbersome. Agreed on all points. --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list. --===============2431221064463181914== MIME-Version: 1.0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: 7bit
  • status: open --> closed
  • Comment:

Fixed in [#8110]

[tickets:#4900] comment moderation UI needs work [ss488]

Status: closed
Milestone: unreleased
Labels: support p3 moderation ux
Created: Tue Sep 11, 2012 03:18 PM UTC by Chris Tsai
Last Updated: Fri Dec 05, 2014 04:48 AM UTC
Owner: nobody

[forge:site-support:#488]

the sf 2.0 moderation queue lacks links to the tickets. this makes it quite hard to use, as the tiny diff for each moderation entry sometimes doesnt seem to contain the relevant spam.

additionally, some moderation items just say (no subject) for some reason i dont understand--so i dont even know what ticket they are for.

the moderation queue needs to always link to the ticket in question.

finally, in the ticket thread itself, if i see "post awaiting moderation", i should also see the comment in question, marked as pending moderation somehow. if i am in a thread and i see something that needs moderation, but have no way of knowing what the content is, i can't moderate it. am i supposed to go to the moderation queue and hunt through it for the ticket number? I guess I have to, because thats where the button would be to junk it.

This interface is quite cumbersome.

Agreed on all points.

Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/

To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.

--===============2431221064463181914==-- --===============3548239380783845807==--