Improve usability of match scheduling

[GoogleCodeExporter]

There are a few issues with match scheduling page

1) Tournaments should be listed with the most recent first and as default
2) The default round should be round 1 (to reduce the number of "finals"). 
3) The default team player's should match the selected tournament if possible. 
4) The listed teams should be listed by most recent tournament first. 
5) Need to check but the search should try to match teams in the same 
tournament first. 

Original issue reported on code.google.com by doublesk...@gmail.com on 7 Dec 2011 at 8:47

[GoogleCodeExporter]

fixed (2) in r911.

The others will have to wait a bit.

Original comment by Nimda...@gmail.com on 15 Dec 2011 at 1:16

• Changed state: Started

[GoogleCodeExporter]

I've fixed #1 in the DS branch, because I've updated the 
Coach::allowedNodeAccess to add ORDER BY 1 desc, 2 desc, 3 desc to the query. 
I'm happy to apply this to the main, but the impact will be universal (which is 
what I was really after anyway). 

#4 also fixed. I modified the coach::getTeams to order by descending team_id 
instead of name - so a coach's most recently created team gets listed first. 
I've also cleaned up the ouput so there is no optgroupt if the division is 0. 

Original comment by doublesk...@gmail.com on 6 Jan 2012 at 1:07

[GoogleCodeExporter]

This issue was updated by revision r920.

Changes could be applied to the main, but effect the ordering of all 
league/division/tournament nodes so probably need socialisation first. 

Original comment by doublesk...@gmail.com on 6 Jan 2012 at 1:09

[GoogleCodeExporter]

r942 fixes points:
1 - by re-arranging the node list sorting (I agree with you on this)
3+4 - the selected tour limits the "my team"-selection list to those teams 
which can play the tour, and also sorts these teams by largest team_id (ie. 
newest team).
5 - search now only returns team which can play in the selected tour.

please verify this works

Original comment by Nimda...@gmail.com on 16 Oct 2012 at 3:22

• Changed state: Solved

[GoogleCodeExporter]

I'll close this now. None seem to have reported problems.

Original comment by Nimda...@gmail.com on 29 Oct 2012 at 11:18

• Changed state: Fixed