Back to bug 38095

Who When What Removed Added
januszop 2024-10-04 18:29:43 UTC CC januszop
januszop 2024-10-04 18:30:09 UTC CC pmis
lucas 2024-10-07 20:22:35 UTC CC lucas
emily.lamancusa 2024-10-10 19:00:35 UTC Status NEW Needs Signoff
Patch complexity --- Trivial patch
januszop 2024-10-10 19:12:28 UTC Status Needs Signoff Signed Off
januszop 2024-10-10 19:12:30 UTC Attachment #172668 Attachment is obsolete 0 1
anneli.osterman 2024-11-15 06:59:21 UTC Status Signed Off Failed QA
CC anneli.osterman
anneli.osterman 2024-11-15 10:59:34 UTC Status Failed QA Signed Off
m.de.rooy 2025-02-21 10:00:41 UTC Status Signed Off Passed QA
m.de.rooy 2025-02-21 10:00:44 UTC Attachment #172669 Attachment is obsolete 0 1
m.de.rooy 2025-02-21 10:00:53 UTC CC m.de.rooy
QA Contact testopia m.de.rooy
katrin.fischer 2025-02-21 15:44:30 UTC Version(s) released in 25.05.00
Status Passed QA Pushed to main
katrin.fischer 2025-02-21 16:13:33 UTC Keywords release-notes-needed
emily.lamancusa 2025-02-24 13:16:48 UTC Text to go in the release notes This enhancement allows branch information to be included in predefined notices templates for the `Patrons (custom message)` module, which defines notices that can be sent to patrons by clicking the "Add Message" button on the patron account. These notices can now use the `branch` tag to access information about the branch the staff member is logged into at the time they send the message. For example: `[% branch.branchname %]` - the logged-in branch's name, `[% branch.branchaddress1 %]` - the logged-in branch's address, etc.
emily.lamancusa 2025-02-24 13:17:20 UTC Keywords release-notes-needed

Back to bug 38095