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 8EB67E34C for ; Thu, 17 Jan 2013 14:02:34 +0000 (UTC) Received: (qmail 46066 invoked by uid 500); 17 Jan 2013 14:02:34 -0000 Delivered-To: apmail-incubator-bloodhound-dev-archive@incubator.apache.org Received: (qmail 46033 invoked by uid 500); 17 Jan 2013 14:02:33 -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 46017 invoked by uid 99); 17 Jan 2013 14:02:33 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Jan 2013 14:02:33 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [209.85.216.43] (HELO mail-qa0-f43.google.com) (209.85.216.43) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Jan 2013 14:02:26 +0000 Received: by mail-qa0-f43.google.com with SMTP id cr7so4277403qab.2 for ; Thu, 17 Jan 2013 06:02:05 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=zksApNXo0SOVtds/d/pRYNQf7nF7H4NADapostWzn5k=; b=ZMCQspAoF5MMiQQtmr8bvyaUkAafHF06o2oy5dJ6rDXj3MUHlFVHM4zVx1XUq3ROcP t0cdhMmnsSSTLjGgWnyWdosDxEfPc++dYMe8t5tz9C1q/N229y/a7pT1900SVnl/a/lO mV2084FC7AhMvCeQSWFGBubMDEy1q8y+6ry92KZXEtfiXiKnQFeEeYMkLYnTZdcU+17/ fdOjIAvBbi0D9JC3oFsuOMrSHWZ+NJ2/RUFR9ZGj7JNP5uBDiI17d2LRLhoL0zkgnrwD 5sNgtTOK4Qy0zr2dIye+S4JYN7kHWZo5xJx7VTHNgtdCC5lSh0jpZ/YF/ls5RrQD8c7N QRkA== MIME-Version: 1.0 X-Received: by 10.224.216.65 with SMTP id hh1mr5587063qab.43.1358431325027; Thu, 17 Jan 2013 06:02:05 -0800 (PST) Received: by 10.49.6.73 with HTTP; Thu, 17 Jan 2013 06:02:04 -0800 (PST) Date: Thu, 17 Jan 2013 15:02:04 +0100 Message-ID: Subject: User comments on ticket modification UI From: Andrej Golcov To: bloodhound-dev@incubator.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQkzZQBQj9/vzWN3RU5BcBYPcI4dhpMEIfCDjdvBDl+g3Wtk34KBBzo8uQ2+ndIZjkut/L5d X-Virus-Checked: Checked by ClamAV on apache.org I showed BH 0.4 UI to a friend of mine in order to get kind of user feedback. My friend is familiar with other issue trackers and uses a few of them (mainly JIRA and Techexcel) on a daily basis. He was mainly confused with current Modify Ticket UI. Please find below a few his comments on this subject from a user prospective: - "Submit changes" button is located under "Add a comment button" while user would expect this button at least before " Change History". - If ticket has a few history records user scrolls down to "Submit changes" button and can't see edit fields, clicking on "Submit changes" saves ticket in background but user can't see that UI is switched to read-only mode and sees "Submit changes" button again. User is confused that nothing was happened and press "Submit changes" button again and again. - "Add comment" and Workflow are expected to be separate action and not part of Modify Ticket flow. Especially simultaneous ticket editing and adding a comment was confusing, given that adding a comment is separate action in read-only mode. - User would expect Cancel of "Modify ticket" mode next by Submit button. It was hard to find Cancel on the top of page near workflow button. It looks like Cancel action cancel workflow action. - Scroll spy bar acts confusing in "Modify Ticket" mode: - After user clicks "Modify ticket", Overview is active - When user scrolls down to find "Submit" button all other options are active except "Modify ticket" - Find summary edit field was not easy. User would expect that all edit fields would be located below spy scroll bar. His suggestions for Modify Ticket mode: - Move Submit/Save button on top of page, where Cancel is located - Remove comments related staff. It is clear that ticket modification UI is in process of improvement. But I think that it is worth sharing these comments with community. Regards, Andrej