New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Training Request list selection not preserved between operations #1375

karenword opened this Issue Oct 16, 2018 · 1 comment


None yet
2 participants

karenword commented Oct 16, 2018

A couple of observations on features/bugs of the select boxes on the Training Requests list pages:

  1. Selected boxes are not preserved between list screens. This means that no more than the number of displayed records may be selected for a bulk action at one time (unless an entire filtered set is desired in which case box selection is unnecessary). This is ok, but at least for my workflow it would be preferable to have selections carry over between search screens for a single bulk action.

  2. The box at the top that selects all records behaves unpredictably. If it is selected on a freshly displayed output screen, the "download selected to CSV" feature downloads ALL applications (not just that screen, not just filtered, ALL applications). If, however you select this box, then alter selections below (say, deselect and select a box) THEN the download includes only those selected on the display screen. This is manageable when you're aware of it, but might cause trouble down the road.


This comment has been minimized.


pbanaszkiewicz commented Oct 17, 2018

Hello @karenword,

The issue 2. was fixed as part of #1374.

The issue 1. is quite hard for me to implement for now, but it was raised a few times before. I have some general ideas, but for v2.2 it cannot happen. I'll keep the issue concentrated on this matter, though.

@pbanaszkiewicz pbanaszkiewicz changed the title from Training Request list select box features to Training Request list selection not preserved between operations Oct 17, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment