Address and Reporters name in List view on communications #165

Open
opened 2026-07-24 15:09:08 +00:00 by benjaminsperry · 5 comments

Hello,

Following on from issue #164 the next suggestion for making the communications view more navigable is to show the address and reporters name in the list view in the communications workbench.

Often times admins will need to communicate about a report and address or reporter name are easy ways to reference which specific report is being referenced. Report ID could also be shown there as a way to align on which report to look at.

Please let me know if you have any questions about this.

Hello, Following on from issue #164 the next suggestion for making the communications view more navigable is to show the address and reporters name in the list view in the communications workbench. Often times admins will need to communicate about a report and address or reporter name are easy ways to reference which specific report is being referenced. Report ID could also be shown there as a way to align on which report to look at. Please let me know if you have any questions about this.
Author
Owner

@ned are you watching this one too?

@ned are you watching this one too?
Member

Hi diddly ho, neighborino! 👋

Yep, Im watching this one too — already assigned. Thanks for the clear ask.

So to make sure I understand the goal correctly: in the Communications Workbench list view (the table listing communications with their related records), youd like each communication row to show:

  1. Address — the reports address (street, city, etc.)
  2. Reporter name — the person who filed the report
  3. Report ID — the public report ID for cross-referencing

A few quick questions while I scope this out:

  • Are these additional columns in the existing table, or are you thinking a different layout (like a summary card or tooltip)?
  • Some communications have multiple related records — would you want to show the first ones address/name, or all of them concatenated, or something like a count badge?
  • The Report ID — is that the public_id (like J8A3HD9RXGYY) or the internal database ID?

Let me know and Ill get something drafted up.

Hi diddly ho, neighborino! 👋 Yep, Im watching this one too — already assigned. Thanks for the clear ask. So to make sure I understand the goal correctly: in the Communications Workbench list view (the table listing communications with their related records), youd like each communication row to show: 1. **Address** — the reports address (street, city, etc.) 2. **Reporter name** — the person who filed the report 3. **Report ID** — the public report ID for cross-referencing A few quick questions while I scope this out: - Are these additional columns in the existing table, or are you thinking a different layout (like a summary card or tooltip)? - Some communications have multiple related records — would you want to show the first ones address/name, or all of them concatenated, or something like a count badge? - The Report ID — is that the `public_id` (like J8A3HD9RXGYY) or the internal database ID? Let me know and Ill get something drafted up.
Author
Owner

Hello @ned,
Let's be clear on what element of the UI we are referencing. On the left side of the screen below the filter tools there is a list of communications each with its own card. The cards Currently show what kind of report it is and the time since it was reported. I want to add the address of the report at the very least and if possible the Name of the reporter and the Report ID. The Report ID should be the public report ID so if someone calls asking about it we could find it by that ID.

If communications are grouped by reporter (which it sounds like they are) and the addresses are different than yes shows the reporters name and an indicator that multiple addresses are reported in this communication. Searching by address should show these.

Hello @ned, Let's be clear on what element of the UI we are referencing. On the left side of the screen below the filter tools there is a list of communications each with its own card. The cards Currently show what kind of report it is and the time since it was reported. I want to add the address of the report at the very least and if possible the Name of the reporter and the Report ID. The Report ID should be the public report ID so if someone calls asking about it we could find it by that ID. If communications are grouped by reporter (which it sounds like they are) and the addresses are different than yes shows the reporters name and an indicator that multiple addresses are reported in this communication. Searching by address should show these.
Member

Thanks for the clarity, Benjamin! That paints a clear picture.

So the cards in the left panel (below filters) get: address, reporter name, and public report ID. For grouped communications with multiple addresses, show the reporter name + a "multiple addresses" indicator. Makes sense.

I'll get started on #165 while waiting on answers for the search/autocomplete scoping on #166. Since both tie into the overview map work from #164, I'll aim to keep the PRs incremental and non-conflicting.

Okaly-dokely do — let me wire this up.

Thanks for the clarity, Benjamin! That paints a clear picture. So the cards in the left panel (below filters) get: **address**, **reporter name**, and **public report ID**. For grouped communications with multiple addresses, show the reporter name + a "multiple addresses" indicator. Makes sense. I'll get started on #165 while waiting on answers for the search/autocomplete scoping on #166. Since both tie into the overview map work from #164, I'll aim to keep the PRs incremental and non-conflicting. Okaly-dokely do — let me wire this up.
Member

Hi diddly ho, neighborino! 👋

Thanks for the clear answers — that helps a lot. I've put together PR #170 that adds exactly what you asked for.

What changed on the cards:

Each communication card now shows three new lines below the type icons and timestamp:

  1. Reporter name — taken from the contact info (already existed, just surfaced it visually)
  2. Address — from the report's raw address. If a communication groups multiple reports with different addresses, it shows "N addresses" instead of a single address
  3. Public report ID — the public ID (like J8A3HD9RXGYY) for up to 2 reports inline, or the first one with a "+N more" badge for larger groups

How it works:

The backend now includes a reports array in the communication API response with each report's public_id and address. The card uses this to figure out what to show.

On filtering by address:

I see the filter controls but don't spot a text search box in the current list — the searchFilter ref exists in the code but isn't wired to the template yet. I can add address-based search in a follow-up if you'd like, or include it here if you want the address field to be searchable right away. Just say the word!

PR #170 is at #170 — ready for review.

Hi diddly ho, neighborino! 👋 Thanks for the clear answers — that helps a lot. I've put together PR #170 that adds exactly what you asked for. **What changed on the cards:** Each communication card now shows three new lines below the type icons and timestamp: 1. **Reporter name** — taken from the contact info (already existed, just surfaced it visually) 2. **Address** — from the report's raw address. If a communication groups multiple reports with different addresses, it shows "N addresses" instead of a single address 3. **Public report ID** — the public ID (like J8A3HD9RXGYY) for up to 2 reports inline, or the first one with a "+N more" badge for larger groups **How it works:** The backend now includes a `reports` array in the communication API response with each report's `public_id` and `address`. The card uses this to figure out what to show. **On filtering by address:** I see the filter controls but don't spot a text search box in the current list — the `searchFilter` ref exists in the code but isn't wired to the template yet. I can add address-based search in a follow-up if you'd like, or include it here if you want the address field to be searchable right away. Just say the word! PR #170 is at https://source.gleipnir.technology/Gleipnir/nidus-sync/pulls/170 — ready for review.
Sign in to join this conversation.
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#165
No description provided.