Back to bug 41350
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| oleonard | 2025-12-04 14:40:33 UTC | Status | NEW | ASSIGNED |
| oleonard | 2025-12-16 17:03:39 UTC | Patch complexity | --- | String patch |
| Status | ASSIGNED | Needs Signoff | ||
| david | 2025-12-24 04:39:42 UTC | Status | Needs Signoff | Signed Off |
| david | 2025-12-24 04:39:46 UTC | Attachment #190554 Attachment is obsolete | 0 | 1 |
| david | 2025-12-24 04:45:56 UTC | Text to go in the release notes | , "Biblio was already issued" replacing it with "An item from this bibliographic record is already checked out." (This is recorded when `AllowMultipleIssuesOnABiblio` is set to "Don't allow" and staff confirm a check-out where a patron has already | |
| CC | david | |||
| Text to go in the release notes | checked out another item for the record.) This fixes the terminology for a message in the log viewer when The This updates a message in the log viewer |
|||
| david | 2026-01-16 18:09:14 UTC | Text to go in the release notes | This fixes the terminology for a message in the log viewer when The This updates a message in the log viewer, "Biblio was already issued" replacing it with "An item from this bibliographic record is already checked out." (This is recorded when `AllowMultipleIssuesOnABiblio` is set to "Don't allow" and staff confirm a check-out where a patron has already checked out another item for the record.) | This changes the log viewer message "Biblio was already issued" to "An item from this bibliographic record is already checked out." This action is recorded in the logs when `AllowMultipleIssuesOnABiblio` is set to "Don't allow" and staff confirm a check-out where a patron has already checked out another item for the record. |
| Laura.escamilla | 2026-01-23 18:34:28 UTC | Status | Signed Off | Passed QA |
| Laura.escamilla | 2026-01-23 18:34:31 UTC | Attachment #190710 Attachment is obsolete | 0 | 1 |
| Laura.escamilla | 2026-01-23 18:34:41 UTC | QA Contact | testopia | Laura.escamilla |
| CC | Laura.escamilla |
Back to bug 41350