This current assignee doesn't stand out well in the ticket details modal, we could make is clearer by making the label bold?
Created attachment 166073 [details] [review] Bug 36760: Use 'strong' for 'Assignee' label This patch simply add the 'strong' class to the assignee label in the catalog concerns display ticket modal.
Created attachment 166090 [details] [review] Bug 36760: Use 'strong' for 'Assignee' label This patch simply add the 'strong' class to the assignee label in the catalog concerns display ticket modal. Signed-off-by: David Nind <david@davidnind.com>
One thing I noted, was that if you access the details dialog box from the catalog record (concerns tab), it doesn't display the assignee. This was with afresh browser, with the cache cleared. Maybe the concern title should be strong as well? Testing notes (using KTD): 1. Set the CatalogConcerns system preference to 'Allow'. 2. Using the staff interface, add a catalog concern for any record: Record > New > New catalog concern. Enter a title, some details for teh description, and click 'Submit'. 3. Access the catalog concerns area in the staff interface home page: . From the home page: click 'Catalog concerns pending' link at the bottom of the page, OR . Go to Cataloguing > Reports > Catalog concerns. 4. Click the 'Details' action for the concern you created. 5. Assign the concern: . For the 'Change assignee' field select a patron . Click 'Update' 6. Click the details action again, and note that the 'Assignee' label in the top right-hand side is plain text. 7. After applying the patch (flush_memcached, and restart_all), refresh the catalog concerns listing page, and click on the details action again. The assignee label should now be in bold
Picked from QA queue, reviewed and tested.
Pushed for 24.05! Well done everyone, thank you!
Wow, this one went quick! :) > One thing I noted, was that if you access the details dialog box from the catalog record (concerns tab), it doesn't display the assignee. This was with afresh browser, with the cache cleared. That one is handled in bug 36757 :)
Depends on Bug 35657 not in 23.11.x
Nothing to change in the manual for this one.