https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31028
David Nind <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #214 from David Nind <[email protected]> --- Here are the things I noted from testing. See the draft test plan posted as a separate comment - I have referred to these notes where appropriate. [1] Wording for system preferences: - for OpacCatalogConcerns "..staff client." should be "..staff interface.". - most notes are formatted as NOTES: in bold [2] If the CatalogConcerns system preference is not enabled (with all of these also disabled: suggestions, OPACReportProblem, and AllowCheckoutNotes), then on the staff interface home page pending concerns are not shown. However, if any of suggestions, OPACReportProblem, or AllowCheckoutNotes are enabled and they have an active item(s), then it is displayed. Note: I had mixed results with this - sometime it worked, other times it didn't, so it was a bit confusing! [3] Viewing the details for a concern in the staff interface (Details action) - on the "Ticket details" for a concern: - there is a line after the text inside the border for the ticket details info - there are no line breaks, so whatever is entered appears as a continuous line [4] Clicking on resolve or comment does nothing: there is an error in the web developer tools console: Uncaught ReferenceError: logged_in_user_borrowernumber is not defined <anonymous> http://127.0.0.1:8081/intranet-tmpl/prog/js/modals/display_ticket_22.0600075.js:75 jQuery 2 dispatch handle [5] Things I noted about the staff report a concern modal: - The width is very narrow (maybe more related to the new staff interface design) - If the CatalogConcernHelp has some HTML, such as a bulleted list after the existing paragraph, then this doesn't display correctly - displays to the right of the paragraph without any bullets (bold seem to display OK) - There is no title field, as there is on the OPAC (not sure whether this is an issue, or what will be displayed in the list of concerns - The buttons are Confirm and Cancel (in the OPAC they are Submit and Cancel) - Nothing happens when clicking Confirm - the web developer tools console shows an error: XHR POST http://127.0.0.1:8081/api/v1/tickets 400 Bad Request [6] On Tools > Patrons and circulation > Notices and slips for the new notices: . the new notices are listed under module "catalog" (with a small "c" - all the other notice modules are shown in sentence case, so this should perhaps be "Catalog". . For TICKET_ACKNOWLEDGEME, maybe the code could be just TICKET_ACKNOWLEDGE in the yaml file as the 'NT' is cut off and not displayed . Note that for the sample notices, TICKET_ACKNOWLEDGEMENT is used, but this is shortened when added to the database to TICKET_ACKNOWLEDGEME [7] I'm not sure what permissions are required for non-super librarian staff to see and manage catalog concerns. Initially I thought it was manage_problem_reports permission - but then I started getting mixed results. On some occasions on the Cataloguing home page, the option Reports > Catalog concerns was still displayed. Clicking on this sends you to a login box that says "Error: You don't have permission to access this page". See also step 8.4. [8] Editing the catalog concern help text and concern templates: - If you use the WYSIWYG editor to edit the concern template: the mark up (such as <br/>s, <li>s, etc) is displayed in the form input area when reporting a concern from the OPAC and staff interface - Does this mean we can only edit the concern template using the text editor? - If you use the WYSIWYG editor to edit the help text: some mark up is not displayed correctly in the staff interface, for example: after adding a bulleted list after the first paragraph, on the modal the list is displayed to the right of the paragraph without the bullets. (Initially it didn't display correctly in the OPAC, but this was probably a browser caching issue.) [9] Display of concerns on a record page in the staff interface - no details listed: I created some concerns for a record - the tab shows the number, but the list only shows the table header row and no concern details. [10] CatalogerEmails: it appears you can add multiple email addresses - is a comma used to separate these? [11] Sidebar menu when in the Catalog concerns area: currently displays the Tools sidebar, now needs to be the Cataloguing sidebar menu, along with the page title. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
