Release notes SoloDB 5.14.6

[FEATURE] A reservation can now consume multiple quota rules in consumption order. If the first rule does not have enough tokens, SoloDB automatically allocates the remainder from the next applicable rule instead of requiring the user to split the reservation.

[IMPROVEMENT] Quota rules are evaluated against the requested booking period. SoloDB selects the combination that fits the requested slot instead of moving the reservation to a time where the first rule can cover it completely.

[IMPROVEMENT] Booking proposals now show the tokens available before the booking, tokens already consumed, tokens usable during the requested period, the amount allocated by each rule, and the balance after the booking. Error messages explain which rule is short and by how many tokens.

[IMPROVEMENT] Authorized users can select an applicable quota rule from the schedule's power-edit view. Changing the rule recalculates the proposal and records the decision in the job changelog.

[FIX] Weighted reservation duration is now calculated from the equipment's quota configuration, preventing an incorrect token cost when the selected quota rule refers to a different quota header.

[FEATURE] Users can transfer all or part of a locked, unfinished advanced reservation to a colleague. The sender selects a recipient and time range, may add a message, and can revoke the request while it is pending.

[FEATURE] Transfer recipients can accept or reject a request from their profile. An accepted request splits the reservation at the selected boundaries and moves the relevant quota consumption to the recipient. The original reservation remains locked throughout the process; the recipient's quota may become negative when insufficient tokens remain.

[IMPROVEMENT] Pending and completed transfers are visible from the reservation schedule, user profile, and administrator job details. Notifications include the correct job, equipment, requester, recipient, period, status, and response information.

[IMPROVEMENT] Equipment configured for trained and in-training users now consistently includes both groups in reservation access, user lists, and transfer-recipient selection.

[IMPROVEMENT] Calendar events now use the user's reservation colour with automatically selected readable text. Tentative bookings have a clear badge and lighter appearance, locked bookings are visually distinct, and the current user's bookings have a Me badge.

[IMPROVEMENT] Calendars now respect the configured time zone and use an updated FullCalendar scheduler and theme, with refreshed day headers, toolbar controls, resource handling, and timeline styling.

[IMPROVEMENT] Reservation exports now include fractional duration in hours, the linked job/reservation identifier, and token cost for advanced bookings.

[FIX] Reservations linked to a service event can no longer be deleted separately. The reservation dialog explains this and links to the service event where the related records can be managed together.

[FEATURE] Organisation groups can be configured with their own annual run-number sequence. New runs created from the web application, monitor flows, or API use either the group sequence or the shared yearly sequence according to this setting.

[IMPROVEMENT] The per-group run-number setting is shown on group details and included in group exports and API data.

[SYSTEM] Added a run:recalculate-run-numbers command for recalculating one group's run labels or all run labels. Changes are transactional, recorded in each run's changelog, and queued for search-index updates.

[FIX] Run parts are returned in a stable root-and-ID order in substrate views.

[IMPROVEMENT] Converting an existing root location into storage equipment now uses a dedicated confirmation flow. The new equipment inherits the location's name, code, active status, room, and zone group, and the initiating user is stored as its creator.

[FEATURE] Existing equipment can now create and link its own root storage location. The new location inherits the equipment's name, number, active status, and zone group, and the equipment is moved to that location.

[IMPROVEMENT] Storage-equipment conversion validates permissions and prevents invalid links, including non-root locations, locations or equipment that are already linked, main equipment in a setup, missing zone groups, and duplicate location names or codes.

[IMPROVEMENT] Locations now display a consistent formatted identifier such as L000123; the location list exposes that identifier in a sortable ID column.

[IMPROVEMENT] Substrate forms hide the location field when the installation has no locations configured, while continuing to preserve or clear the field correctly when locations are available.

[FIX] Deleting equipment now also removes the main module from the search index, preventing a detached or "floating" module from remaining visible.

[UI] Equipment-module navigation now uses the parsed module type name, active modules have a clearer status badge, and the create button has been restored to the chemical list.

[CHANGE] Removed obsolete search facets for equipment reservation availability and building active/room status so the available filters match supported search behaviour.

[FIX] Automatic service-announcement emails are recorded permanently per service and mailing, preventing them from being sent again after 24 hours. The obsolete mailing interval setting has been removed from the data model and UI.

[FIX] Service mailings now select the nearest unfinished upcoming event, regardless of environment, and include the correct event, service, and equipment identifiers. When no upcoming event exists, the next scheduled date is derived from the latest executed event.

[FIX] Deleting a service event cleans up its linked reservations in the search index. Events with attached documents are protected from deletion, and event details no longer assume that a report version exists.

[FEATURE] Label-layout containers can now have an optional background colour. The colour is shown in the layout editor and rendered in PDFs for chemical containers, equipment, equipment modules, locations, rooms, and zones.

[SYSTEM] FullCalendar scheduler and theme updated to v7.1.0, with improved day headers, and better dark mode support