Communication card: show address, reporter name, and public report ID #170

Closed
ned wants to merge 1 commit from issue-165-address-reporter-list-view into main
Member

Adds address, reporter name, and public report ID to the communication list cards in the Communications Workbench.

Backend changes:

  • Added Address field to RelatedRecord struct, populated from report's AddressRaw
  • Added communicationReport struct (public_id, address)
  • Communication JSON response now includes a reports array with public_id and address for every report in the communication

Frontend changes:

  • Added CommunicationReport class and DTO
  • Communication cards now show:
    • Reporter name (from contact)
    • Address (or "N addresses" indicator when multiple distinct addresses exist)
    • Public report IDs (up to 2 shown inline, more shown as "+N more")

Closes #165

Adds address, reporter name, and public report ID to the communication list cards in the Communications Workbench. **Backend changes:** - Added `Address` field to `RelatedRecord` struct, populated from report's AddressRaw - Added `communicationReport` struct (`public_id`, `address`) - Communication JSON response now includes a `reports` array with public_id and address for every report in the communication **Frontend changes:** - Added `CommunicationReport` class and DTO - Communication cards now show: - Reporter name (from contact) - Address (or "N addresses" indicator when multiple distinct addresses exist) - Public report IDs (up to 2 shown inline, more shown as "+N more") Closes #165
eliribble force-pushed issue-165-address-reporter-list-view from 4242445570
All checks were successful
/ golint (push) Successful in 20s
/ pnpm-build (push) Successful in 1m8s
to 22fc442cee
All checks were successful
/ golint (push) Successful in 19s
/ pnpm-build (push) Successful in 1m29s
2026-08-29 22:18:16 +00:00
Compare
eliribble closed this pull request 2026-10-13 18:29:34 +00:00
All checks were successful
/ golint (push) Successful in 19s
/ pnpm-build (push) Successful in 1m29s

Pull request closed

Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
2 participants
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
Gleipnir/nidus-sync!170
No description provided.