Bug 36760 - Make 'Current assignee' stand out more in ticket details view
Summary: Make 'Current assignee' stand out more in ticket details view
Status: Pushed to main
Alias: None
Product: Koha
Classification: Unclassified
Component: Staff interface (show other bugs)
Version: unspecified
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Martin Renvoize
QA Contact: Testopia
URL:
Keywords:
Depends on: 35657
Blocks:
  Show dependency treegraph
 
Reported: 2024-05-02 14:28 UTC by Martin Renvoize
Modified: 2024-05-07 09:20 UTC (History)
2 users (show)

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


Attachments
Bug 36760: Use 'strong' for 'Assignee' label (1.12 KB, patch)
2024-05-02 14:31 UTC, Martin Renvoize
Details | Diff | Splinter Review
Bug 36760: Use 'strong' for 'Assignee' label (1.16 KB, patch)
2024-05-02 20:58 UTC, David Nind
Details | Diff | Splinter Review

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Renvoize 2024-05-02 14:28:42 UTC
This current assignee doesn't stand out well in the ticket details modal, we could make is clearer by making the label bold?
Comment 1 Martin Renvoize 2024-05-02 14:31:50 UTC
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.
Comment 2 David Nind 2024-05-02 20:58:41 UTC
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>
Comment 3 David Nind 2024-05-02 21:11:52 UTC
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
Comment 4 Katrin Fischer 2024-05-06 09:09:41 UTC
Picked from QA queue, reviewed and tested.
Comment 5 Katrin Fischer 2024-05-06 09:19:15 UTC
Pushed for 24.05!

Well done everyone, thank you!
Comment 6 Martin Renvoize 2024-05-07 09:20:06 UTC
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 :)