androidlover5842/TrisolarisPMS
1
0
Fork 0
Code Issues 22 Pull Requests Actions Packages Projects 1 Releases Wiki Activity

Room Stays: Add rooms to an existing booking (pre-assign stay) #1

New Issue
Open
opened 2026-02-08 20:27:59 +05:30 by androidlover5842 · 0 comments
androidlover5842 commented 2026-02-08 20:27:59 +05:30
Owner
Copy Link

Goal

  • From Booking Details -> Room Stays, allow adding an extra room stay to the same booking (future stay allocation).

API

  • POST /properties/{propertyId}/bookings/{bookingId}/room-stays (pre-assign stay)

UX requirements

  • Select room (from available rooms for date range).
  • Pick from/to (date+time) aligned with billing policy if applicable.
  • Optional: nightly rate + rate source + rate plan code + currency + notes.
  • Validate date range (toAt > fromAt).
  • Block occupied rooms with clear error.

Engineering requirements

  • Follow Room DB sync rule: UI action -> server request -> Room DB update -> UI reacts from Room observers.
  • After success: refresh Room caches (booking details + active stays + booking list if needed) via shared helper (no copy-paste).
  • No duplicate mapping/permission checks across screens.

Acceptance

  • New room stay appears in Room-backed booking details and room-stays list without manual refresh.
Goal - From Booking Details -> Room Stays, allow adding an extra room stay to the same booking (future stay allocation). API - POST `/properties/{propertyId}/bookings/{bookingId}/room-stays` (pre-assign stay) UX requirements - Select room (from available rooms for date range). - Pick from/to (date+time) aligned with billing policy if applicable. - Optional: nightly rate + rate source + rate plan code + currency + notes. - Validate date range (`toAt > fromAt`). - Block occupied rooms with clear error. Engineering requirements - Follow Room DB sync rule: `UI action -> server request -> Room DB update -> UI reacts from Room observers`. - After success: refresh Room caches (booking details + active stays + booking list if needed) via shared helper (no copy-paste). - No duplicate mapping/permission checks across screens. Acceptance - New room stay appears in Room-backed booking details and room-stays list without manual refresh.
androidlover5842 added the featureroom-stayuxapiroom-db-sync labels 2026-02-08 20:27:59 +05:30
androidlover5842 added this to the TrisolarisPMS Roadmap project 2026-02-09 00:56:03 +05:30
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
ai-ocr
AI / OCR / parsing automation
 api
API / contract / retrofit
 availability
Availability / inventory / allocation
 bug
Bug / regression
 compliance
Compliance / audit / legal requirements
 feature
User-facing functionality
 finance
Cashbook / expenses / settlements
 guest
Guest profile & identity flows
 guest-docs
Guest documents (upload/view/delete)
 hr-payroll
Staff, attendance, payroll
 integration
3rd party integrations / automation
 privacy
Privacy, consent, sensitive data handling
 room-db-sync
Must follow Room DB sync rule
 room-stay
Room stay management
 security
Security / permissions / sensitive data
 telephony
Call-related UX/integrations
 ux
User experience / UI polish
 voice-ai
Speech-to-text / voice extraction
No Label api feature room-db-sync room-stay ux
Milestone
No items
No Milestone
Projects
Clear projects
No project TrisolarisPMS Roadmap
Assignees
Clear assignees
androidlover5842
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: androidlover5842/TrisolarisPMS#1
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?