Return-Path: X-Original-To: apmail-incubator-allura-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-allura-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 44B0010FE6 for ; Wed, 10 Jul 2013 20:08:03 +0000 (UTC) Received: (qmail 52378 invoked by uid 500); 10 Jul 2013 20:08:03 -0000 Delivered-To: apmail-incubator-allura-dev-archive@incubator.apache.org Received: (qmail 52366 invoked by uid 500); 10 Jul 2013 20:08:03 -0000 Mailing-List: contact allura-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: allura-dev@incubator.apache.org Delivered-To: mailing list allura-dev@incubator.apache.org Received: (qmail 52357 invoked by uid 99); 10 Jul 2013 20:08:03 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Jul 2013 20:08:03 +0000 X-ASF-Spam-Status: No, hits=-0.1 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of noreply@sourceforge.net designates 216.34.181.60 as permitted sender) Received: from [216.34.181.60] (HELO smtp.ch3.sourceforge.com) (216.34.181.60) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Jul 2013 20:07:57 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sourceforge.com; s=x; h=Date:Message-ID:Subject:Reply-To:From:To:MIME-Version:Content-Type; bh=DiUmqYFYBeuvY8YVm6S1mDeC00rPYOMcm8qHktTVDeM=; b=LCl73fYI32utLAoj90nL0dCzOxawljKsMJgVzPJK5MKc9SWP+Wbnh6BEpTP3Vq0qor3u/XrsANr5zN5PILOKT7HPLiU0+bTRQD9eUhfyW8FTgmwFL7v24xGiZTQBYaDNUk8NYGaoViVhYhkkPxQ3w6XRjOzqT8z94j6UM5odVeQ=; Received: from localhost ([127.0.0.1] helo=sfs-alluradaemon-1.v29.ch3.sourceforge.com) by sfs-alluradaemon-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Ux0fo-0000Mv-Dd for allura-dev@incubator.apache.org; Wed, 10 Jul 2013 20:07:36 +0000 Content-Type: multipart/related; boundary="===============6925630057947484286==" MIME-Version: 1.0 To: "[allura:tickets] " <4900@tickets.allura.p.re.sf.net> From: "Dave Brondsema" Reply-To: "[allura:tickets] " <4900@tickets.allura.p.re.sf.net> Subject: [allura:tickets] #4900 comment moderation UI needs work [ss488] Message-ID:

Date: Wed, 10 Jul 2013 20:07:36 +0000 X-Virus-Checked: Checked by ClamAV on apache.org --===============6925630057947484286== Content-Type: multipart/alternative; boundary="===============3835674622507986958==" MIME-Version: 1.0 --===============3835674622507986958== MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Thanks for the feedback, Peter. I've grabbed a screenshot of what I see for reference when we work on this later: http://screencast.com/t/uFCJlGFKdJcx Looks like we need to make sure the link on the right is fully visible, and an easy way to see the full content of the post on the moderation page. (If you click on the link on the right column, it'll go to the post where you can see the full post and also approve it from there) --- ** [tickets:#4900] comment moderation UI needs work [ss488]** **Status:** open **Labels:** support p3 moderation ux **Created:** Tue Sep 11, 2012 03:18 PM UTC by Chris Tsai **Last Updated:** Wed Jul 10, 2013 07:41 PM 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 sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list. --===============3835674622507986958== MIME-Version: 1.0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: 7bit

Thanks for the feedback, Peter. I've grabbed a screenshot of what I see for reference when we work on this later: http://screencast.com/t/uFCJlGFKdJcx

Looks like we need to make sure the link on the right is fully visible, and an easy way to see the full content of the post on the moderation page. (If you click on the link on the right column, it'll go to the post where you can see the full post and also approve it from there)


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

Status: open
Labels: support p3 moderation ux
Created: Tue Sep 11, 2012 03:18 PM UTC by Chris Tsai
Last Updated: Wed Jul 10, 2013 07:41 PM 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 sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/

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

--===============3835674622507986958==-- --===============6925630057947484286==--