ChiliProject is not maintained anymore. Please be advised that there will be no more updates.
We do not recommend that you setup new ChiliProject instances and we urge all existing users to migrate their data to a maintained system, e.g. Redmine. We will provide a migration script later. In the meantime, you can use the instructions by Christian Daehn.
Change the order of the (possible) watchers list on issue creation (Feature #1060)
Description
When creating a new ticket, the watchers list is currently ordered alphabetically, first from left to right, then from top to bottom. This works perfectly, but if there are many users in the project, this list is really hard to use. The problem is that the data is shown in several columns, and therefore the human brain automatically groups them "by column" and not "by row", which makes it VERY hard to find a certain person! It would be much better to sort the list of (possible) watchers in the following way: alphabetically, first from top to bottom, and then from left to right
old:
Alice Bob Claire Dave Eve George Hugh Jessica Mike Paul Tim
new:
Alice Eve Mike Bob George Paul Claire Hugh Tim Dave Jessica
History
Updated by Andrew Smith at 2012-07-04 01:35 pm
I think this could be a great example of using Select2 - http://ivaynberg.github.com/select2/#multi
It would mean with JS you'd have a select list that you'd have to ctrl-click on to select multiple people though.
Updated by Felix Schäfer at 2012-07-09 06:39 pm
Andrew Smith wrote:
I think this could be a great example of using Select2 - http://ivaynberg.github.com/select2/#multi
It would mean with JS you'd have a select list that you'd have to ctrl-click on to select multiple people though.
I'd like it more than pushing my mouse around I think though, and the UI could be unified between the watcher selectors and even the user selectors in general.
Would select2 allow for something like the current watcher selector in the issue sidebar, i.e. an "auto compete driven" select list? That would probably make the multiselect more discoverable.
Updated by Felix Schäfer at 2012-07-09 06:48 pm
Fabian, I like the idea, I fear the limitation is one of html though. The current columns in the list "happen" automagically because one user+select-box doesn't fill the whole width of the container they're in, thus the following ones are added on the same row until they fill the space available. Presenting the users sorted in columns rather than rows would means that we would need to know how many columns there will be once the page is rendered, hence I can't think of a good way to do that on the server.
Andrew: do you know of any html tricks that could make that happen at least for newer browser until there's a better user selector?