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 <[email protected]>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 <[email protected]>**
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
