From bloodhound-dev-return-857-apmail-incubator-bloodhound-dev-archive=incubator.apache.org@incubator.apache.org Fri Oct 5 11:44:18 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 C1362DEDB
for ; Fri, 5 Oct 2012 11:44:18 +0000 (UTC)
Received: (qmail 577 invoked by uid 500); 5 Oct 2012 11:44:18 -0000
Delivered-To: apmail-incubator-bloodhound-dev-archive@incubator.apache.org
Received: (qmail 484 invoked by uid 500); 5 Oct 2012 11:44:16 -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 442 invoked by uid 99); 5 Oct 2012 11:44:14 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Oct 2012 11:44:14 +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 gary.martin@wandisco.com designates 209.85.214.47 as permitted sender)
Received: from [209.85.214.47] (HELO mail-bk0-f47.google.com) (209.85.214.47)
by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Oct 2012 11:44:06 +0000
Received: by mail-bk0-f47.google.com with SMTP id jk7so807922bkc.6
for ; Fri, 05 Oct 2012 04:43:45 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=google.com; s=20120113;
h=message-id:date:from:user-agent:mime-version:to:subject:references
:in-reply-to:content-type:x-gm-message-state;
bh=oaxIduc/FS7GKHdnnp98dnXVA/hcV0d437dPCx8GnO4=;
b=N/FL2JUkbvmLhZuQe+dyWYej8mmQZF3wtgqiDIfc8vzZ+2oZtKCXjwJhB85aYPOG7h
vrw9NlmmJuUzxD93sUcj0GQUozyZ9nXVHfYo51t+X1gv3RMvkou5nstbu1NxTwAuP5mk
+duuVdnTDAyhzDazo4JANNYdfNbArMIyCzxdD2AO00WfOnfmKSqw8WlAATUnHHUCGXrZ
N4CAz12kmjy4H4ReR4TAU0bEXcIEr4AXAkvGTpAKWBc/tGv7Z/t8JslyNqX3l+BSIctc
1T5Itd+XgpqeLQVji3Be4q1+DcgYMpeP844M8a1iesrXg0kCjnh/3l2lAA3cJ8r80t84
tC1Q==
Received: by 10.204.145.214 with SMTP id e22mr2606655bkv.133.1349437425468;
Fri, 05 Oct 2012 04:43:45 -0700 (PDT)
Received: from [10.2.5.205] ([77.86.30.139])
by mx.google.com with ESMTPS id j24sm7451370bkv.0.2012.10.05.04.43.44
(version=SSLv3 cipher=OTHER);
Fri, 05 Oct 2012 04:43:44 -0700 (PDT)
Message-ID: <506EC7EC.3020302@wandisco.com>
Date: Fri, 05 Oct 2012 12:43:40 +0100
From: Gary Martin
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120912 Thunderbird/15.0.1
MIME-Version: 1.0
To: bloodhound-dev@incubator.apache.org
Subject: Re: dashboard ticket query ordering
References: <506DA300.4010002@wandisco.com> <506EA000.6010406@wandisco.com>
In-Reply-To:
Content-Type: multipart/alternative;
boundary="------------090506010004000306080400"
X-Gm-Message-State: ALoCoQmILB3UlEcKfepfTCnZYZXsskO9FM3L7b8tZclyX+w6xYEcbXn4N3+7A8aZ9q8O3kKjkffn
--------------090506010004000306080400
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Well, I think we are thinking along the same lines here. The additional
question is then what the ordering of milestones should be. Clearly the
original reasoning would suggest that it would be chronologically or
alphabetically, of which I would prefer to use due-date.
I was under the impression that ordering by milestone would not make use
of the due-date but further tests suggest it is working the way I would
hope. So, something like the following would propably do the job for the
two queries on the top level dashboard (swaps "group=time" for
"group=milestone" and dropping "groupdesc=1" from both):
Index: bloodhound_dashboard/bhdashboard/web_ui.py
===================================================================
--- bloodhound_dashboard/bhdashboard/web_ui.py (revision 1392307)
+++ bloodhound_dashboard/bhdashboard/web_ui.py (working copy)
@@ -193,10 +193,10 @@
None,
{'args' : {
'max' : 10,
- 'query' :
'status=!closed&group=time&' \
- 'col=id&col=summary&col=owner' \
+ 'query' :
'status=!closed&group=milestone'\
+ '&col=id&col=summary&col=owner' \
'&col=status&col=priority&' \
- 'order=priority&groupdesc=1&desc=1',
+ 'order=priority&desc=1',
'title' : 'Active Tickets'}}],
'altlinks' : False
},
@@ -206,10 +206,10 @@
None,
{'args' : {
'max' : 10,
- 'query' :
'status=!closed&group=time&' \
- 'col=id&col=summary&col=owner' \
+ 'query' :
'status=!closed&group=milestone'\
+ '&col=id&col=summary&col=owner' \
'&col=status&col=priority&' \
- 'order=priority&groupdesc=1&desc=1&' \
+ 'order=priority&&desc=1&' \
'owner=$USER',
'title' : 'My Tickets'}
}],
We would not be able to show the due-date of the milestone at the moment
and so the milestone name would appear in place of the date on the left
hand side. Would this be a problem for anyone?
Cheers,
Gary
On 05/10/12 10:19, Peter Koželj wrote:
> If as a user I do not have the ability to change the ordering, I would
> probably prefer first by milestone and then by priority. At least for "My
> Tickets" that is, for "All Tickets" that might depend on my role (developer
> vs. project manager for instance).
>
> On the other hand, without showing what the actual sorting order is, users
> will assume that it is either chronologically or alphabetically. So if it
> is neither of the two, actual ordering needs to be presented to the user
> somehow.
>
> Peter
>
> On Fri, Oct 5, 2012 at 10:53 AM, Gary Martin wrote:
>
>> I think that the ability to reorder would be good, along with user
>> configurability in the long run, but I would still like to see the initial
>> ordering being more helpful. If we are not able to order tickets sensibly
>> on the top level dashboard at this point, I would wonder how a user would
>> manage it.
>>
>> Cheers,
>> Gary
>>
>>
>>
>> On 05/10/12 08:53, Peter Koželj wrote:
>>
>>> If we are only talking about ordering, why not just enhance the widgets so
>>> that if the user clicks on a column title, that is the field that the
>>> results are sorted by? What is in dashboard definition would only be the
>>> default then.
>>>
>>> In to long run we need user configurable dashboard as well as user
>>> configurable widgets.
>>>
>>> Peter
>>>
>>> On Thu, Oct 4, 2012 at 4:53 PM, Gary Martin **
>>> wrote:
>>>
>>> Hi,
>>>> As I understand it, we want the dashboard view to show a list of tickets
>>>> that is likely to be interesting to the viewer. In order to focus in we
>>>> will probably need additional plugins for watched tickets, ticket due
>>>> dates
>>>> and so on. However, given that these plugins could be turned off or
>>>> ignored, we should probably already be looking at making sure that we
>>>> have
>>>> a reasonable order for the tickets.
>>>>
>>>> At the moment the queries are in ticket created order and the main way
>>>> that this is mitigated is that we have one list of "My Tickets" and one
>>>> for
>>>> "Active Tickets". I was wondering whether we could order the tickets by
>>>> milestone due date while we don't have ticket due dates but this appears
>>>> to
>>>> require a custom report. Secondary ordering should probably be by ticket
>>>> priority for the moment.
>>>>
>>>> Does this sound reasonable for now?
>>>>
>>>> Cheers,
>>>> Gary
>>>>
>>>>
--------------090506010004000306080400--