Unique identifier of the user to whom this request is assigned for completion and ownership. Accepts user IDs in either base64url-encoded format (URL-safe base64 using A-Z, a-z, 0-9, dash, underscore without padding, example 'u7YtMp2kQxRvN9LmW4HzAg') or GUID format (128-bit identifier with hyphens, example '56d7d33f-1d42-461b-85eb-26b7b2872c88'). Use this field to delegate request responsibility to specific team members, track workload distribution, and enable assignee-based filtering and notifications. Set to null to explicitly unassign the request, leaving it available for manual assignment or routing. When updated, the system typically sends assignment notifications to the new assignee and updates the request in their work queue. Assignee must have appropriate permissions to view and work on requests in the specified space. Changing assignee does not affect request status or other properties unless workflow rules trigger additional actions.

Human-readable title or name of the request providing a concise summary of what is being requested or the work to be completed. This string field serves as the primary identifier in UI listings, search results, notifications, and reports, helping users quickly understand request purpose without viewing full details. Use clear, descriptive titles that communicate the request's objective such as 'Create Q1 Product Launch Materials', 'Review Sales Enablement Content', or 'Update Customer Training Documentation'. Typical length ranges from 5-100 characters for optimal display across interfaces. Set to null to leave the title unchanged during partial updates, or provide new text to update the request name. Title changes are immediately reflected in all views and may trigger update notifications to followers and assignees.

Unique identifier of the program that this request is associated with or belongs to, enabling requests to be linked to larger program initiatives for tracking, reporting, and organizational purposes. Accepts program IDs in base64url-encoded format (example 'xH75yTE6xmz6MUvcTDxIRi') or GUID format (example '12345678-1234-1234-1234-123456789abc'). Use this field to associate requests with programs for program-level reporting, dependency tracking, and initiative alignment. When a request is linked to a program, it appears in the program's request list and contributes to program metrics and completion tracking. Set to null to disassociate the request from any program, making it a standalone request. Program must exist in the same space and user must have permissions to associate requests with it. Changing programId updates program associations immediately and may affect program metrics and dashboards.

Priority level classification indicating the relative urgency and importance of the request for resource allocation and completion sequencing. Allowed values are 'low' (routine requests with flexible timelines), 'medium' (standard priority for typical requests), 'high' (important requests requiring expedited attention), or 'critical' (urgent requests needing immediate action and highest resource priority). Use priority to influence work queue ordering, enable priority-based filtering and reporting, and communicate urgency to assignees and stakeholders. Priority typically affects default sort order in work lists, notification urgency, SLA calculations, and escalation thresholds. Set to null to leave priority unchanged during updates. Changing priority may trigger notifications to assignees and followers, update dashboard metrics, and influence automated routing decisions. Example use case includes escalating priority from 'medium' to 'critical' when customer deadlines accelerate.

Textual note or message providing context, explanation, or commentary about the request update, particularly useful when changing status, priority, or assignments. This note field is typically included in system-generated notifications sent to assignees, followers, and stakeholders when the request is updated, helping recipients understand the reason for changes or additional context about the request state. Use for communicating update rationale such as 'Priority increased due to customer escalation', 'Reassigned based on subject matter expertise', or 'Extended due date pending stakeholder approval'. Set to null to update the request without adding explanatory notes. Notes appear in notification emails, activity feeds, and audit logs providing transparency about why changes were made. Typical length ranges from one sentence to a short paragraph (10-200 words) to maintain readability in notifications.