https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28396 Katrin Fischer <katrin.fischer@bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Signed Off |Failed QA QA Contact|testopia@bugs.koha-communit |katrin.fischer@bsz-bw.de |y.org | --- Comment #5 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- Something is not quite right here for me. As we have no callnumbers in the sample data, I copied the itemnumber into itemcallnumber, set cn_source to z (generic) and ran touch_all_items so set cn_sort. For me the main purpose of the callnumber browser is to quickly determine if a callnumber has already been used. If it's used, you have a red line, if it's free, you see a green line where the callnumber would be. 1) Existing: Search for 26 Old: You get the red markup for 26. 26 shows between 259 and 260 as expected. New: Same. OK. 2) Not existing: Search for 1000 Old: Green line between 100 and 101 as expected. New: You see the green line on top of the table, before 1, you are no longer seeing the "before and after" correctly. Not OK. 3) Existing, not on first page: Search for 500 Old: You get the red markup for 500. 500 shows between 50 and 501 as expected. New: You see the page with the first numbers, no clue red or green as the number is on a much later page. You can page there... (not nice) or you can use the table search - more clicks and you don't see the before and after. Not OK. 2) Modal For me the window is a bit too small now and the table doesn't resize properly when the window size is increased (maybe side effects of the new staff design?) 3) Sorting cn_sort should be used for sorting on the call number column. -- You are receiving this mail because: You are watching all bug changes.