feat(assets): surface CMDB expansion fields on the detail panel (PMS-454) #323

Merged
YousifShkara merged 1 commit from feat/PMS-454-cmdb-asset-fields into main 2026-06-24 06:38:01 +02:00
Owner

Extends RemoteAsset with the eight CMDB columns the server now ships (assigned_user_id, assigned_user_name, ip_address, hostname, mac_address, installed_date, department, in_transit_ticket_id) and renders each on the asset detail page's left-column dl grid alongside the existing Type / Company / Manufacturer / Model / Serial / Asset Tag rows. Each new row renders only when populated so an older asset that pre-dates the migration does not show a "-" row of placeholders.

The In-Transit ticket renders as a Link to the ticket detail page so a tech moving an asset can jump to the tracking ticket without leaving the asset view.

Companion to the server-side PR feat/PMS-454-cmdb-asset-expand which adds the migration + AssetResponse + service queries. The edit-form fields (assigned-user picker, IP input, hostname input, etc.) follow in a sibling PR - this captures the read surface so the QA can verify the data round-trips through the API as soon as the server merges.

#PMS-454

Extends `RemoteAsset` with the eight CMDB columns the server now ships (assigned_user_id, assigned_user_name, ip_address, hostname, mac_address, installed_date, department, in_transit_ticket_id) and renders each on the asset detail page's left-column dl grid alongside the existing Type / Company / Manufacturer / Model / Serial / Asset Tag rows. Each new row renders only when populated so an older asset that pre-dates the migration does not show a "-" row of placeholders. The In-Transit ticket renders as a Link to the ticket detail page so a tech moving an asset can jump to the tracking ticket without leaving the asset view. Companion to the server-side PR `feat/PMS-454-cmdb-asset-expand` which adds the migration + AssetResponse + service queries. The edit-form fields (assigned-user picker, IP input, hostname input, etc.) follow in a sibling PR - this captures the read surface so the QA can verify the data round-trips through the API as soon as the server merges. #PMS-454
feat(assets): surface CMDB expansion fields on the detail panel (PMS-454)
All checks were successful
Check / fmt + clippy + tests (pull_request) Successful in 8m22s
Create release / Create release from merged PR (pull_request) Has been skipped
34e74e93a7
Extends `RemoteAsset` with the eight CMDB columns the server now ships (assigned_user_id, assigned_user_name, ip_address, hostname, mac_address, installed_date, department, in_transit_ticket_id) and renders each on the asset detail page's left-column dl grid alongside the existing Type / Company / Manufacturer / Model / Serial / Asset Tag rows. Each new row renders only when populated so an older asset that pre-dates the migration does not show a "-" row of placeholders.

The In-Transit ticket renders as a Link to the ticket detail page so a tech moving an asset can jump to the tracking ticket without leaving the asset view.

Companion to the server-side PR `feat/PMS-454-cmdb-asset-expand` which adds the migration + AssetResponse + service queries. The edit-form fields (assigned-user picker, IP input, hostname input, etc.) follow in a sibling PR - this captures the read surface so the QA can verify the data round-trips through the API as soon as the server merges.

#PMS-454
YousifShkara deleted branch feat/PMS-454-cmdb-asset-fields 2026-06-24 06:38:01 +02:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
psa-systems/mokosh-apps!323
No description provided.