On the root page (pools index), filter view:
when clicking on 'Deployments', 'Instances' or 'Pools' tabs, all these URLs points are served by Pools#index action. e.g. when I click on 'Deployments', AJAX requests fetches list of deployments from:
/pools?details_tab=deployments&only_tab=true&view=filter

but backbone is configured to fetch data from url:
/deployments

This is generally bad, because a user can potentially get 2 different lists of data (since requests are served by 2 different actions).

sql query used for backbone request is:
Deployment.includes(:owner).apply_filters(:preset_filter_id => params[:deployments_preset_filter], :search_filter => params[:deployments_search]). list_for_user(current_user, Privilege::VIEW).where('deployments.pool_id' => @pools).order(sort_column(Deployment, "deployments.name") +' '+ sort_direction).paginate(:page => params[:page] || 1)


Especially paginate at the end causes that only first 25 deployments will be returned when using backbone.


sql query used when clicking on tab:
@deployments = Deployment.apply_filters(:preset_filter_id => params[:deployments_preset_filter], :search_filter => params[:deployments_search]).              list_for_user(current_user, Privilege::VIEW).list(sort_column(Deployment), sort_direction)


Good news is that tabs + backbone are now only on pools index page.

Simpler hotfix solution:
- make sure that both deployments and pools controllers use same sql query when fetching data.

Cleaner solution:
- change backbone route for deployments/instances/pools so it will fetch deployments through the same url which is used when clicking on a tab.
this involves 2 steps:
- proper json response on pools#index action
- update some of our JS funcs which take care of passing URL params - from what I know from Jirka, URL params are not passed properly when doing backbone ajax request