Report details

The report details page shows everything about a single report: its description, attachments (photos, video, audio, documents), precise location on the map, activity and updates, and any assigned team or owner.

Primary sections

• Header: report title, public ID, status (open/closed), and quick actions (share, copy ID, follow).
• Location: map centered on the report's pin; controls to open the full map, recenter, or view nearby reports.
• Attachments: view images, play videos/audio, or download documents. Use the gallery to step through photos and see timestamps.
• Activity: chronological feed of actions (submitted, assigned, status changes, comments, photos added). Each entry shows who performed it and when.
• Actions: follow, add a comment, change status, assign to a team or person (if you have permissions).

How to use

• Inspect attachments first — photos are often the quickest way to understand the issue.
• Use the map pin to confirm location; click the map-pin control to open the full Reports map centered on this report.
• Read the activity feed to see whether the report has been triaged, assigned, or updated.
• Use the share or copy-ID actions to reference this report in other systems or correspondence.

Map behaviour

• The report page centers the map on the report's coordinates. The map may show nearby reports or cluster markers depending on zoom.
• Use the zoom controls to explore the surroundings; clicking nearby markers opens those reports.

Privacy & attachments

• Attachments are user-provided content. Respect privacy: do not publicly republish content that identifies private information without consent.
• Download attachments only when necessary; treat uploaded media as potentially sensitive.

Pages & components

• src/app/[locale]/reports/[publicId]/page.tsx — server page that fetches the report data and composes the view.
• Report viewer components: attachment gallery, map viewer, activity feed, and action controls.

APIs

• GET /reports/:publicId — fetch full report details including attachments, location, activity, and metadata.
• POST /reports/:publicId/comments — add a comment to the report (requires authentication).
• PATCH /reports/:publicId — update status, assignment, or other editable fields. Request body example: { status?: string, assignedTo?: string, note?: string }.

Developer notes

• Fetch the report server-side to allow proper indexable pages and authenticated fetches that forward cookies.
• The attachments payload should include URLs and MIME types; generate thumbnails for images to speed rendering.
• Ensure the map component accepts explicit coordinates and can optionally request nearby reports (use bbox queries) for contextual markers.
• Activity entries should be paginated or lazy-loaded for long histories.
• Implement optimistic UI for comment posting with a short-lived local entry and reconciliation on server response.

If you want this page to appear in the help index, the slug to match is reports/report.