#596: pagination on /dashboard confused
------------------------+--------------------
  Reporter:  tim        |      Owner:  nobody
      Type:  defect     |     Status:  new
  Priority:  major      |  Milestone:
 Component:  dashboard  |    Version:  0.6.0
Resolution:             |   Keywords:
------------------------+--------------------
Changes (by tim):

 * version:   => 0.6.0


Old description:

> When viewing the product-less url of /dashboard the page number links
> result in a search for tickets of the default product.  However, that
> page shows a list of all product tickets so you'd expect to get later
> pages of that same list.

New description:

 When viewing the product-less url of /dashboard the page number links
 result in a search for tickets of the default product.  However, that page
 shows a list of all product tickets so you'd expect to get later pages of
 that same list.

 Further clarification
 ------------------------
 What seems to work correctly:
 A url such as "/products/mainserver/dashboard" shows all the tickets for
 the product "mainserver".  If there are further pages a search is
 initiated and shows that page of "mainserver" tickets.

 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.
 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 probably leads into a further issue of there being no apparent way of
 doing a search across all products.

--

-- 
Ticket URL: <https://issues.apache.org/bloodhound/ticket/596#comment:5>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker

Reply via email to