Bug #91

Intentions browsing bugs

Added by Eric Harris-Braun over 2 years ago. Updated about 2 years ago.

Status:Closed Start date:09/30/2009
Priority:Urgent Due date:
Assignee:JF Noubel % Done:

0%

Category:- Spent time: -
Target version:0.1-seed
Tags:

Description

The most visible is that pagination doesn't show any navigation. So if you get more than 30 intentions you only see the 30 first ones. As "paginate results" is checked by default, this was the most disconcerting for everyone.
Also, ordering by date of creation doesn't help because it's an increasing order, so you get older intentions first. Maybe we'd want to reverse the order ?
The match radio-buttons (requester/offerer) is something people have a hard time remembering, probably because they didn't check it in the first place. Maybe showing everything by default, with a color/icon/column to indicate if it's a request or an offer, then allowing people to refine their search by showing only either, would help.
Last, when you navigate away from the intentions list by clicking on an intention to show its contents, then go back to the list, the match is lost, so you're back to offers.

So let aside possible improvements, I think unchecking "paginate results" and reverse-order by creation date should greatly improve immediate usability.

History

Updated by JF Noubel about 2 years ago

  • Priority changed from Normal to Urgent
  • Target version changed from 0.2-alpha to 0.1-seed

Putting it in seed and urgent, as current flowplace practitioners don't see the intentions they have placed, and don't see other's intentions, unless they know they have to uncheck the paginate checkbox and click on search again. So right now this is very limiting and blocking the whole practical functionality

Updated by Eric Harris-Braun about 2 years ago

  • Status changed from New to Fixed
  • Assignee changed from Eric Harris-Braun to JF Noubel

changed defaults for listing intentions to no pagination and newest first sorting.

Please break out other items from this ticket into a new ticket for any other refinements

Updated by JF Noubel about 2 years ago

  • Status changed from Fixed to Closed

From fixed to closed

Also available in: Atom PDF