Bug 40819 - Guided reports select column should not be initialized as select2
Summary: Guided reports select column should not be initialized as select2
Status: Needs Signoff
Alias: None
Product: Koha
Classification: Unclassified
Component: Reports (show other bugs)
Version: Main
Hardware: All All
: P5 - low trivial
Assignee: Brendan Lawlor
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-09-16 17:41 UTC by Brendan Lawlor
Modified: 2025-09-16 17:54 UTC (History)
1 user (show)

See Also:
GIT URL:
Change sponsored?: ---
Patch complexity: Trivial patch
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:


Attachments
Bug 40819: Only initialize select2 for #report_param_form (1.58 KB, patch)
2025-09-16 17:54 UTC, Brendan Lawlor
Details | Diff | Splinter Review

Note You need to log in before you can comment on or make changes to this bug.
Description Brendan Lawlor 2025-09-16 17:41:52 UTC
This is a follow up from bug 37050.

To reproduce:
1. Go to Reports > Create guided report
2. Click Next >>
3. Click Next >>
3. Notice the form has been initialized as select2
Comment 1 Brendan Lawlor 2025-09-16 17:54:08 UTC
Created attachment 186503 [details] [review]
Bug 40819: Only initialize select2 for #report_param_form

This patch makes the the css selector specifically target the
report_param_form in guided reports

To test:
1. Go to Reports > Create guided report
2. Click Next >>
3. Click Next >>
3. Notice the form has been initialized as select2
4. Apply patch and refresh the page
5. Confirm the select column form is back to normal
6. Confirm select2 is still initialized for SQL reports
   example: select * from items where homebranch IN <<Library|branches:in>>