Return-Path: X-Original-To: apmail-incubator-bloodhound-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-bloodhound-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 EAE93EF0B for ; Wed, 20 Feb 2013 20:46:27 +0000 (UTC) Received: (qmail 57085 invoked by uid 500); 20 Feb 2013 20:46:27 -0000 Delivered-To: apmail-incubator-bloodhound-dev-archive@incubator.apache.org Received: (qmail 57031 invoked by uid 500); 20 Feb 2013 20:46:27 -0000 Mailing-List: contact bloodhound-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: bloodhound-dev@incubator.apache.org Delivered-To: mailing list bloodhound-dev@incubator.apache.org Received: (qmail 57021 invoked by uid 99); 20 Feb 2013 20:46:27 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Feb 2013 20:46:27 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of joachim.dreimann@wandisco.com designates 74.125.82.50 as permitted sender) Received: from [74.125.82.50] (HELO mail-wg0-f50.google.com) (74.125.82.50) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Feb 2013 20:46:20 +0000 Received: by mail-wg0-f50.google.com with SMTP id es5so6657506wgb.17 for ; Wed, 20 Feb 2013 12:45:59 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type:x-gm-message-state; bh=CkS7J1ZBO030QI7ka20uPjiuiU5+JZ8+vH3Qke9pp40=; b=NM60tHw75KiM7O4qTxgkP8tBxA3SUhUbKP0nmo1tRDoD05PWuz06+hNBxpX7qLOOu3 S4oTbBuiAk2exyIW2M9m4VmXaQarFk7GAj8sz5MXe6KhovZS7EF49CUAO4Oy1ljNKP0Y ueXw+QGQ98/Gzb5FhfPngLOrnWW9ou1EYBiXFRNLOvHIBe8mzx2PDfLroD7fglRIwS7g U3p8Rcj8jm5Cs2z2OMWEFo7tJWoZqudwyhQLicsnLpUnmbtD4oROI7JaQtTHbfm+AbuY CY2UpDgjKcjjq405rQO+LF3KUuQvfdTG8p4l5C6wJP/ziSGzB6OR7qVJiWcljSm9nVsy /Fhg== MIME-Version: 1.0 X-Received: by 10.194.108.101 with SMTP id hj5mr36807455wjb.6.1361393159042; Wed, 20 Feb 2013 12:45:59 -0800 (PST) Received: by 10.194.45.234 with HTTP; Wed, 20 Feb 2013 12:45:58 -0800 (PST) In-Reply-To: References: <50F91C2A.6010307@wandisco.com> <51080E48.10604@wandisco.com> <49BB52D9-1E72-4549-962E-F497DA589E34@gmail.com> <51123500.5020105@wandisco.com> <51129463.9010500@wandisco.com> Date: Wed, 20 Feb 2013 20:45:58 +0000 Message-ID: Subject: Re: User comments on ticket modification UI From: Joachim Dreimann To: "bloodhound-dev@incubator.apache.org" Content-Type: multipart/alternative; boundary=047d7bf10a36a4f86804d62e0b42 X-Gm-Message-State: ALoCoQlwOZ3Tm8JfpT3qCtUnipp/qo0yNf3DIo13iSWjNfkeNtved2x5eVijVDfBl5zGtzxzK7FW X-Virus-Checked: Checked by ClamAV on apache.org --047d7bf10a36a4f86804d62e0b42 Content-Type: text/plain; charset=ISO-8859-1 Apologies for the long delay and brevity, but I suggest that we: *1. Remove the local navigation / scrollspy bar.* Multiple people have mentioned that it is there to solve a problem that shouldn't exist in the first place (and often doesn't). Personally I never use it. *2. Use only the #breadcrumbbar as the sticky header.* This still gives users a good indication as to what they're looking at, without taking up as much space and giving them some quick options. We may want to make its parent sticky too on large screens to keep meta navigation and search in view. *3. Add the ability to leave a comment to the top of the activity feed. *That will make it easier/quicker to leave comments when editing the ticket and replying to recent comments by others (which are already shown at the top of the activity feed). *4. Separate the workflow and save actions.* The confusion caused by having both the word Update and the next workflow status in the same button has been raised by many. The workflow status should be changed via a popover element from the Status property. *5. Enable editing of the ticket summary as a contentEditable field, rather than a text input box. *Currently the heading style changes beyond all recognition when it goes from

to , which can be disorientating. Cheers, Joe On 6 February 2013 19:04, Olemis Lang wrote: > On 2/6/13, Gary Martin wrote: > > > [...] > > > > Interestingly, in the current version we appear to have the > > add-a-comment field above the change history. > > > [...] > > > Is ticket UI in trunk @ HEAd really working ? > > https://issues.apache.org/bloodhound/ticket/366 > > jftr , I've never been able to see it in action > :'( > > so I'd like to know if you can reproduce that error . > > > > -- > Regards, > > Olemis. > > Blog ES: http://simelo-es.blogspot.com/ > Blog EN: http://simelo-en.blogspot.com/ > > Featured article: > -- Joe Dreimann UX Designer | WANdisco * * *Transform your software development department. Register for a free SVN HealthCheck * --047d7bf10a36a4f86804d62e0b42--