Add a comments sidebar & associate comments to specific objects by wes-otf · Pull Request #4923 · HyphaApp/hypha

wes-otf · 2026-07-29T18:49:35Z

Closes #4871. Adds the ability to comment on objects like Project Forms, SOWs, Reports & Invoices via a "mini" comment form in the detail view sidebar for said objects.

This PR also covers a few related yet adjacent things:

Formatting fixes to normalize the detail views between Project Forms, SOWs, Reports & Invoices.
New events for "creating" (first edit) and editing of the Project Forms/SOWs
Tailwind formatting (ie. max-w-[60rem] → max-w-240)

TODO:

Resolve merge conficts
Add/fix unit tests
~~Make status updates to PF/SOW reactive like they are for Invoices~~
~~Associate status updates (ie. approvals) to the ProjectFormPointer instead of the project so they show in the Status & Activity section~~
Unify the CommentForm more to be able to the used for both the comments tab and the comment sidebar

Test Steps

Confirm that...

(as a Staff role) smaller version of the comment form is available as a sticky sidebar item in the detail views for Project Form, Scope of Work, Invoices & Reports.
(as a Staff role) when commenting utilizing the mini form, it shows up in both the "Status & Activity" section and in the "Comment" tab, with a link to the object that was commented on.
detail views between Project Forms, SOWs, Reports & Invoices are all very stylistically similar/the same
statuses & activity are available in the detail view for Project Forms, SOWs, Reports & Invoices and are reactive when a status is updated
an event is created when a PF/SOW is edited for the first time

frjo · 2026-08-11T11:26:30Z

+{% if activities.count > 1  or activities.count == 1 and not preview_activity %}
+    <details class="collapse collapse-arrow group" id="statusDetail" {% if open %}open{% endif %}>
+        <summary class="collapse-title">
+            <h2 class="card-title">{% blocktrans with activity_count=activities.count %}Status & Activity <span class="font-normal text-base-content/70">({{ activity_count }})</span>{% endblocktrans %}</h2>


If possible, avoid tags in translated strings.

what do you think makes the most sense for this? for RTL languages I figured the ability to put the count on the left would be ideal, but can also include the variable in the translation & just remove the formatting, just thought it was slick.

wes-otf · 2026-08-13T15:44:18Z

            {% if not object.is_archive or object.projects.exists %}
                <h2 class="sr-only">{% trans "Add communication" %}</h2>
-                <div class="pb-6 mb-4 w-full border-b border-base-300">
+                <div class="pb-6 w-full border-b border-base-300">


this was causing a gap between the start of the border & the timeline line which is why I removed it here

frjo · 2026-08-19T07:08:28Z

@wes-otf I rebased this on top of main. Hopefully it is a clean rebase. Will do a review as well.

…AF & SOW

…conditional field inclusion with `CommentForm`, small timeline formatting fixes

frjo · 2026-08-21T08:07:52Z

I took the liberty to add some translation fixes to this PR.

wes-otf · 2026-08-24T13:39:35Z

+    """
+    language = get_language() or settings.LANGUAGE_CODE
+    if not language.lower().startswith("en"):
+        return text


This was a great solution for this @frjo - thanks for adding it!

wes-otf · 2026-08-24T13:40:43Z

Looks great to me! Thanks for adding those!