Growers: ability to add notes to a grower

[sebastiangaertner]

Much like in this screenshot we really need to be able to make notes to a grower account. Attached see the solution of Asana

And this is how Hubspot is managing this:

This is certainly a domain migration topic as well since it is part of the advanced user management requirements.

[buddy1974]

Hi team, Marcel here (scrum master). This matches partner requests for a simple internal notes area on each grower (similar to Asana/HubSpot examples in the screenshots). Right now there’s no clean place to write internal remarks about a grower, so people keep side docs/spreadsheets.

The Admin Panel Vision says the Grower module should be the single source of truth and support richer user management. A notes thread on the grower fits that goal (keeps context attached to the record, not scattered).

Acceptance Criteria (aligned with Admin Panel Vision):

Each grower profile shows a Notes section where staff can add short text notes.

Notes are internal-only (not shown on the public map or external views).

I can add, edit, and (if needed) delete my note; edits keep a small history (who changed what/when).

Notes list shows author name, timestamp, newest first; simple, clean UI (think Asana/HubSpot style).

Basic permissions: only authorized Admin Panel users can write/edit notes; viewers without permission can’t.

Notes load fast with the grower detail and don’t break existing data.

Works in production (not just dev), and doesn’t leak to any public API outputs.

Dependencies / links:

Needs a comments/notes API (mentioned earlier on the thread).

Related/duplicate: #669 (this issue should remain the canonical one).

Part of the Grower detail redesign umbrella (#7) and aligned with the Vision doc’s “single source of truth” idea.

If this direction sounds good, I can help tighten the wording and labels once I have triage rights.

[sebastiangaertner]

@buddy1974 are you still keen to find someone to work on this?

[cynthiabondi]

@sebastiangaertner , I did not assign this to anyone as it is a duplicate of 669. But I will assign it to @kaohenry as he is also working on 669 so he can consider this one as well.

[cynthiabondi]

8.4.26 update: frontend PR #1178 is open and awaiting review, backend API is the remaining blocker.