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

HR/Payroll: Flexible work types / job titles (carpenter, electrician, etc.) #18

New Issue
Open
opened 2026-02-09 17:36:20 +05:30 by androidlover5842 · 0 comments
androidlover5842 commented 2026-02-09 17:36:20 +05:30
Owner
Copy Link

Goal

  • Support any kind of worker (carpenter/electrician/plumber/porter/etc.) without hardcoding roles.

Key rule

  • Separate:
    • System Role (permissions): fixed + typed (ADMIN/MANAGER/STAFF)
    • Work Type / Job Title (what they do): flexible, manager-editable

Work

  • Add jobTitle (free text) to worker profile.
  • Optional: WorkType master list:
    • manager can add/edit/disable types (autocomplete + "Add new")
    • store both workTypeId and jobTitle (or derive jobTitle from workType when selected)
  • Ensure worker creation/edit flows allow arbitrary titles.
  • Reporting: filter expenses/attendance/payroll by work type/job title.

Engineering requirements

  • Do not violate typed-role rule: only permissions use enums; job titles are data-driven.
  • Follow Room DB sync rule for profile edits.

Acceptance

  • Manager can record a worker as "Electrician" today and "Carpenter" tomorrow without app changes.
Goal - Support any kind of worker (carpenter/electrician/plumber/porter/etc.) without hardcoding roles. Key rule - Separate: - System Role (permissions): fixed + typed (ADMIN/MANAGER/STAFF) - Work Type / Job Title (what they do): flexible, manager-editable Work - Add `jobTitle` (free text) to worker profile. - Optional: WorkType master list: - manager can add/edit/disable types (autocomplete + "Add new") - store both `workTypeId` and `jobTitle` (or derive jobTitle from workType when selected) - Ensure worker creation/edit flows allow arbitrary titles. - Reporting: filter expenses/attendance/payroll by work type/job title. Engineering requirements - Do not violate typed-role rule: only permissions use enums; job titles are data-driven. - Follow Room DB sync rule for profile edits. Acceptance - Manager can record a worker as "Electrician" today and "Carpenter" tomorrow without app changes.
androidlover5842 added the featureuxhr-payroll labels 2026-02-09 17:36:20 +05:30
androidlover5842 added this to the TrisolarisPMS Roadmap project 2026-02-09 17:36:32 +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 feature hr-payroll 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#18
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?