From bloodhound-dev-return-1397-apmail-incubator-bloodhound-dev-archive=incubator.apache.org@incubator.apache.org Mon Dec 10 12:17:41 2012 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 7D568E24E for ; Mon, 10 Dec 2012 12:17:41 +0000 (UTC) Received: (qmail 9605 invoked by uid 500); 10 Dec 2012 12:17:41 -0000 Delivered-To: apmail-incubator-bloodhound-dev-archive@incubator.apache.org Received: (qmail 9592 invoked by uid 500); 10 Dec 2012 12:17:41 -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 9577 invoked by uid 99); 10 Dec 2012 12:17:40 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Dec 2012 12:17:40 +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 (athena.apache.org: domain of joachim.dreimann@wandisco.com designates 209.85.214.175 as permitted sender) Received: from [209.85.214.175] (HELO mail-ob0-f175.google.com) (209.85.214.175) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Dec 2012 12:17:36 +0000 Received: by mail-ob0-f175.google.com with SMTP id vb8so2161427obc.6 for ; Mon, 10 Dec 2012 04:17:15 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=yj2VYCXuk2/tu+noUGm/tpAtUIOhZD5ULQ//1jg7LnI=; b=Wft+iomyyXYcRs1B2sZKRpt8pIRrGxbPOWcw43gG5psbY5YFnoJvoSVq/DOVynZxfu e5bPVmOHEHkLV067w8HLbmz//Lf4VfEjPFBhVg1LlmKY9fjwO4plf8x29D9GjXrJ2GNo lWvcsyJFx9mU4bseKbGnUfa0VRXriqem4LlN29tkR2qUW8Gpg7uusLqonAuRywoOF5rZ T3daoqm8CGIILng+kK6JzJQj68mKKAHFPduVwrBHbhC4kCj2JAlaMwWFRNv2Kil4JuTC YQvOhg69P1VbNoGAjldSjdz0lwZkQLSawQ3UMZmX/2mzmjRQYUf5ddzApv5OgZRGYBu7 hOMg== MIME-Version: 1.0 Received: by 10.182.212.35 with SMTP id nh3mr7426346obc.10.1355141835397; Mon, 10 Dec 2012 04:17:15 -0800 (PST) Received: by 10.76.141.134 with HTTP; Mon, 10 Dec 2012 04:17:15 -0800 (PST) In-Reply-To: <50C0670A.6040804@digiverse.si> References: <50C0670A.6040804@digiverse.si> Date: Mon, 10 Dec 2012 12:17:15 +0000 Message-ID: Subject: Re: [BEP-0003] Multiproduct UI/UX From: Joachim Dreimann To: bloodhound-dev@incubator.apache.org Content-Type: multipart/alternative; boundary=e89a8f5039dcb8187104d07e8b56 X-Gm-Message-State: ALoCoQlSVLlfKWcKRQyLrg7ls/F9WaTRSnVQRox1hLi+Y4ywlClRpdXidTSLZ13NW5H+NAEvppZu X-Virus-Checked: Checked by ClamAV on apache.org --e89a8f5039dcb8187104d07e8b56 Content-Type: text/plain; charset=ISO-8859-1 This is an important topic, so I felt I had to take some extra time to reply. You'll see my replies to Jure's initial message below, but first let me make clear where I stand: 1. *Dashboard:* There is only one, and it's global. That's the way it was always intended too. As you drill down you'll find Product views, Version views, Milestone views etc, but I believe we should only call one the Dashboard for clarity. 2. *Custom Query and Reports: *Should always have a global scope to start with. That helps users with their mental model of how these things work. 3. *Wiki:* Gary has made strong arguments for keeping the global wiki in the past. That's fine with me. I do believe though that it should be much easier to associate Wiki articles with objects (such as Products, Version and the like), going as far as reserving a namespace in the wiki for each object (product/version/milestone), and linking to it automatically from the object's view. Now to address some specific points: *Andrej*: > What I would expect from global dashboard as a user is quite different to product dashboard: I agree. The scope of what is displayed naturally decreases as the user navigates to increasingly more specific objects. *Gary*: > I can see this working for users with access to multiple products. If a user > only has access to a single product, wouldn't we want them to go directly to > their product dashboard view? In my view: No. To set expectations, make it easier to compare what they see with colleagues and expand their set of objects (ie create a second product) we should show them the same (global) Dashboard. Users can of course always create browser bookmarks directly to the (sole) Product view if they prefer. *Jure:* > * 'My Products' - list of products user is member of, including quick links to tickets&wiki for that specific product > [...] > * 'All Products' - list of all products* * All Products are all products that I am allowed to view as that particular user, making it also 'My Products'. I don't believe we should differentiate between them. The only differentiation then should be based on: 1. Criteria the user selects themselves (ie personal focus) that I don't believe we need to determine in Bloodhound itself, we should just let users have the ability to follow/favourite/pin products. 2. Involvement in the product, especially 'current' involvement: Taking on tickets and completing them vs no tickets assigned to the user gives us a good indication which one may be more important to the user at any given time. This should be exposed in the UI. I will update the Dashboard html mockup this afternoon to make a suggestion and will report back then. Cheers, Joe On 6 December 2012 09:36, Jure Zitnik wrote: > Hi, > > Reading BEP-0003 I realized that we have not yet discussed what the user > interface/experience for the multi-product should actually be. What we > currently have in the proposal are mostly technical/implementation details. > > What I would propose for start is the following: > > 1. Introduction of global dashboard: > * default page/entry point for the user > * layout could be very similar to the current dashboard with some widgets > missing (Versions, Milestones, Components for example) > * Search is global, through all products > * Wiki and Ticket quick links are not available > * Custom query and Reports are available (scope is all products) > * this requires us to support both per-product and global reports > * shows user's tickets - in all products (similar to My Tickets in the > current dashboard but globally) > * shows active ticket's - in all products (as in the current dashboard but > globally) > * 'My Products' - list of products user is member of, including quick > links to tickets&wiki for that specific product > * this might for the time of being be list of all products at least > until we get the per-product permission schemes up > * 'All Products' - list of all products > * Activity tab shows global activity > > 2. Modification of existing tickets/wiki/custom query/reports pages to > support per product scope > > 3. Selecting a product/ticket/wiki/report should change the user interface > scope to the product of the selected ticket/wiki/report etc. > > 4. When in product scope, there should be an indicator in the interface of > the currently active product scope. A mechanism should be put in place to > change product scope easily. > > 5. Prerequisite for the above is that all user-created resources (tickets, > wiki, reports, etc.) have product associated. In turn that means we'll need > to modify the installation to create the default product, modify the > upgrade to migrate existing instances to default product etc. ... but this > is a subject of another discussion thread :) > > This is just to kick the conversation off, I'm aware there are lots of > things I missed (all of the settings section for example,...) ... what I'd > like after the discussion on the dev list is that we are on the same page > regarding UI/UX and that we're able to produce a set of user interface > mockups and update BEP-0003 accordingly... > > Best regards, > Jure > > -- Joe Dreimann UX Designer | WANdisco * * *Transform your software development department. Register for a free SVN HealthCheck * --e89a8f5039dcb8187104d07e8b56--