#596: pagination on /dashboard confused
------------------------+----------------------
Reporter: tim | Owner: olemis
Type: defect | Status: accepted
Priority: major | Milestone:
Component: dashboard | Version: 0.6.0
Resolution: | Keywords:
------------------------+----------------------
Changes (by olemis):
* owner: nobody => olemis
* status: new => accepted
Comment:
Replying to [ticket:596 tim]:
>
[...]
> Further clarification
[...]
>
> What doesn't seem to work correctly:
> A url such as "/dashboard" shows all the tickets for '''all''' products.
If there are further pages a search is initiated and you'd think it would
show that page of '''all product''' tickets, but it doesn't. It instead
does a search based on the default product and only shows tickets
associated with that.
When I read this part I wanted to say I wanted to say «default product
will be phased out soon, that should should solved the issue» ... but that
not the whole truth, just part of the situation. Taken blood-hound.net as
a reference, in there the concept of default product does not exist , and
still atm [http://blood-hound.net/dashboard global dashboard] shows
tickets for products `swlcu` and `dataviz` whereas ''More'' and pagination
links return an [http://blood-
hound.net/query?status=!closed&group=product&col=id&col=summary&col=owner&col=status&col=priority&col=milestone&order=priority
empty result set].
So, there's work to do even after.
> Further, you may notice that the breadcrumbs show "Dashboard / Default"
and think you maybe able to correct it by selecting the product default
and selecting "All Products". However, that only takes you to
"/products".
This will be gone once the notion of default product will be removed. See
[http://blood-
hound.net/query?status=!closed&product=dataviz&groupdesc=1&group=time&order=priority&col=id&col=summary&col=owner&col=status&col=priority&desc=1
this query] , even if does not work as explained above the query is
executed in global scope.
> This probably leads into a further issue of there being no apparent way
of doing a search across all products.
From a developer perspective the fact that the widget shows results
indicates that it's possible to retrieve such result sets (same code used
in the end) . The fact is that /query request handler seems not to be
relying upon `ProductTicketQuery` class ... or if it is there's something
wrong.
I'll take a look .
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/596#comment:6>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
