You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bloodhound.apache.org by Gary Martin <ga...@wandisco.com> on 2012/10/04 16:53:52 UTC
dashboard ticket query ordering
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
Re: dashboard ticket query ordering
Posted by Peter Koželj <pe...@digiverse.si>.
Totally agree on REST api thing! Ideally all data that UI displays should
come through REST web services.
That would give us complete freedom on UI front (UX, multidevice,
technology) and would make Bloodhound easier to integrate into enterprise
environments.
Peter
On Fri, Oct 5, 2012 at 5:27 PM, Olemis Lang <ol...@gmail.com> wrote:
> On 10/5/12, Peter Koželj <pe...@digiverse.si> 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?
>
> +1 ... we'll need them to become more AJAX-ready because IMO this
> should happen without leaving dashboard page . Besides changing order
> is not just about sorting the same rows displayed in first place but
> the whole query result set .
>
> If this has not been implemented before is just because there was no
> much time available and there were other priorities . Indeed previous
> mockups include similar features requiring dynamic updates , even if
> not exactly sorting by field .
>
> OTOH ... we shall see how to make this work with reports ... if not
> already implemented , of course . We'll have to check that .
>
> This , together with #146 and a few more tickets makes me wonder
> whether we should be thinking in adding some generic RESTful
> infrastructure , based on known APIs (e.g. XmlRpcPlugin) . This would
> be quite important to implement dynamic AJAX widgets and speed up the
> process .
>
> > What is in dashboard definition would only be the
> > default then.
> >
>
> +1
>
> > In to long run we need user configurable dashboard
>
> +1
>
> > as well as user
> > configurable widgets.
> >
>
> that's what #83 is for , afaicr .
>
> --
> Regards,
>
> Olemis.
>
> Blog ES: http://simelo-es.blogspot.com/
> Blog EN: http://simelo-en.blogspot.com/
>
> Featured article:
>
Re: dashboard ticket query ordering
Posted by Olemis Lang <ol...@gmail.com>.
On 10/5/12, Peter Koželj <pe...@digiverse.si> 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?
+1 ... we'll need them to become more AJAX-ready because IMO this
should happen without leaving dashboard page . Besides changing order
is not just about sorting the same rows displayed in first place but
the whole query result set .
If this has not been implemented before is just because there was no
much time available and there were other priorities . Indeed previous
mockups include similar features requiring dynamic updates , even if
not exactly sorting by field .
OTOH ... we shall see how to make this work with reports ... if not
already implemented , of course . We'll have to check that .
This , together with #146 and a few more tickets makes me wonder
whether we should be thinking in adding some generic RESTful
infrastructure , based on known APIs (e.g. XmlRpcPlugin) . This would
be quite important to implement dynamic AJAX widgets and speed up the
process .
> What is in dashboard definition would only be the
> default then.
>
+1
> In to long run we need user configurable dashboard
+1
> as well as user
> configurable widgets.
>
that's what #83 is for , afaicr .
--
Regards,
Olemis.
Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/
Featured article:
Re: dashboard ticket query ordering
Posted by Olemis Lang <ol...@gmail.com>.
On 10/5/12, Gary Martin <ga...@wandisco.com> wrote:
[...]
>
> Clearly the
> original reasoning would suggest that it would be chronologically or
> alphabetically, of which I would prefer to use due-date.
>
+1
[...]
> 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):
>
I checked that and it's working ok for me .
>
> 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?
>
... at the moment I state that it's better to get the 90% of it than nothing ;)
If due dates are good to have then we can cheat a little and display
milestone name (due date) when that fields is used to form ticket
groups . In order to get this done we should modify Trac core in a way
similar to what we did before for datetime fields .
--
Regards,
Olemis.
Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/
Featured article:
Re: dashboard ticket query ordering
Posted by Gary Martin <ga...@wandisco.com>.
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 <ga...@wandisco.com>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 <ga...@wandisco.com>**
>>> 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
>>>>
>>>>
Re: dashboard ticket query ordering
Posted by Peter Koželj <pe...@digiverse.si>.
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 <ga...@wandisco.com>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 <ga...@wandisco.com>**
>> 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
>>>
>>>
>
Re: dashboard ticket query ordering
Posted by Gary Martin <ga...@wandisco.com>.
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 <ga...@wandisco.com>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
>>
Re: dashboard ticket query ordering
Posted by Peter Koželj <pe...@digiverse.si>.
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 <ga...@wandisco.com>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
>
Re: dashboard ticket query ordering
Posted by Olemis Lang <ol...@gmail.com>.
On 10/4/12, Gary Martin <ga...@wandisco.com> 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.
>
The more I read these kinds of comments the more I think we really
need to implement custom dashboards (i.e. #140 ) . If not the whole
shiny admin web UI (i.e. #83 ) ... well , at least the mechanisms to
store/load dashboard contents from the DB . Static DASHBOARD_SCHEMA
was ok at the beginning nut now it seems we need a better equivalent
solution .
This is not a dream , especially now that there's a patch for #45 .
> 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".
They are two different things afaicr . The former is like «hey! let me
see what should I do next» whereas the later is about «hey! let me see
what's other people doing» .
> I was wondering whether we could order the tickets
> by milestone due date
+1
> while we don't have ticket due dates but this
> appears to require a custom report.
There are widgets for both , ticket queries & reports . If the scope
of this change is limited to ASF issue tracker then let's just create
the report ... but we'll need a patched of Bloodhound itself (<=
gggrrr ) ... which adds extra $0.02 to my initial comment above . If
scope affects Bloodhound distribution then we should add that report
to the list in trac/db_default.py . IMO this could be a patch we could
propose upstream since it'd be nice to notify trac-dev to include it
for e.g. Trac 1.0.1 .
> Secondary ordering should probably
> be by ticket priority for the moment.
>
+1
> Does this sound reasonable for now?
>
The intent , yes . Details matter .
--
Regards,
Olemis.
Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/
Featured article:
Re: dashboard ticket query ordering
Posted by Joachim Dreimann <jo...@wandisco.com>.
Sounds good to me.
Joe
On 4 Oct 2012, at 15:53, Gary Martin <ga...@wandisco.com> 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