search

Wiredcraft / fullpm

Kanban board for GitHub issues
https://wiredcraft.com/products/fullpm
1 stars 3 forks source link

Sort issues #7

Closed EcutDavid closed 8 years ago

EcutDavid commented 8 years ago

Quite the same with #6, Currently, we just use column-id to decide which board issue should be placed. But we haven't used ranking for sort issues.

For issues which ranking are same, they should be sort alphabetically. For issues with different ranking, should be sort from larger ranking to smaller.

JuhaS commented 8 years ago

This can be done later, lets fix core issues first.

EcutDavid commented 8 years ago

Related code: https://github.com/Wiredcraft/pmhub/blob/68a91bf84281a342072026788a01707be5905056/api/server/models/github-repo.js#L110

Instead of using defaultRanking here, need set ranking alphabetically or based on issue number or whatever.......

ChopperLee2011 commented 8 years ago

seem we do not have solutions about how to set default ranking and how to handle ranking changes, if not, pls info me that, thanks. then IMP

this solution has some problems, one is when user sync the board from github again, the default ranking number will be changed, cause the last update time of these tickets may change in github.

EcutDavid commented 8 years ago

I think issue number is better than update time.

ChopperLee2011 commented 8 years ago
ChopperLee2011 commented 8 years ago

plus: the param nCards in the method above is the sum number of one list (label in our app), and potential bugs maybe JS standard number can only have 16 digits after the decimal point

hunvreus commented 8 years ago
  1. When the board is created, we can pick the default order as being the last updated time (desc).
  2. After that any issue added is added at the end (I suppose) or manually re-sorted by the user.
EcutDavid commented 8 years ago

Done.