| Summary: | Slips should be a message transport type | ||
|---|---|---|---|
| Product: | Koha | Reporter: | Martin Renvoize (ashimema) <martin.renvoize> |
| Component: | Notices | Assignee: | Martin Renvoize (ashimema) <martin.renvoize> |
| Status: | NEW --- | QA Contact: | Testopia <testopia> |
| Severity: | enhancement | ||
| Priority: | P5 - low | CC: | lari.taskula, lisette, lucas |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | All | ||
| GIT URL: | Initiative type: | --- | |
| Sponsorship status: | --- | Comma delimited list of Sponsors: | |
| Crowdfunding goal: | 0 | Patch complexity: | --- |
| Documentation contact: | Documentation submission: | ||
| Text to go in the release notes: | Version(s) released in: | ||
| Circulation function: | |||
| Bug Depends on: | 35285 | ||
| Bug Blocks: | 15278, 36809 | ||
|
Description
Martin Renvoize (ashimema)
2024-05-08 06:35:40 UTC
This would also make it clearer when SlipCSS and NoticeCSS should be used. These are the slips listed as slips in my devbox: Current Code Transport New Code ACCOUNT_SUMMARY print ACCOUNT_SUMMARY AR_SLIP print AR_NEW CHECKINSLIP print CHECKIN HOLD_SLIP email HOLD ISSUEQSLIP email CHECKOUTS OVERDUES_SLIP print ODUE (/first OD notice if different?) PRES_TRAIN_ITEM print -> This doesn't have a corresponding email notice, so we could change this to slip transport type TRANSFERSLIP email-> This doesn't have a corresponding email notice, so we could change this to slip transport type ISSUESLIP email -> -> This doesn't have a corresponding email notice, so we could change this to slip transport type SR_SLIP email -> (This looks like it's more an email than a slip?) +1 It's quite confusing when some slips are currently defined under print type and others under email type. |