feat(backlog ui): surface resolution info on done items (M1 of #31)#5
Merged
Conversation
First milestone of the BL community-engagement design (#31). Adds a "How it was fixed" panel to the BL detail view that shows up whenever selectedItem has a resolution_sha and/or resolution_note (populated via the API surface shipped in #30, commit 6d764b6). Visual: - Emerald-tinted box (matches the "done" status pill color family) - Checkmark icon - "Commit: <sha>" with the SHA hyperlinked to the GitHub commit URL (github.com/akenel/borrowhood/commit/<sha>) - The resolution note rendered below in plain text (whitespace-pre-wrap so multi-line notes display correctly) - Hidden entirely when both fields are empty (no visual noise on in-progress items) No backend change. No JS change. Pure template addition because: - selectedItem already gets the full API response (backlog.js:80) - resolution_sha + resolution_note are now in BacklogItemRead (PR #3) Inserted between the Attachments block and the Activity Trail so it shows up prominently on done items but doesn't interrupt the flow for active ones. Validation: visual only -- will eyeball on staging after deploy. BL-192 and BL-2 have resolution_sha set already (via direct DB UPDATE this morning + via API later) so they'll be the natural test cases when staging shows the new panel. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
M1 milestone of the BL community-engagement design (#31).
Adds a "How it was fixed" panel to the BL detail view that shows up on done items with
resolution_shaorresolution_noteset.Why
Closes the user loop: people who file BL items can now SEE the commit + note that fixed their issue. Until now, even after #30 wired the API, there was no surface for this info — it was buried in the activity log as a COMMENT entry.
Per the design doc (PR #4): M1 is the smallest, highest visual impact milestone. Ship-before-locking-rest per the LP CLI lesson.
Visual
Changes
src/templates/pages/backlog.html— 25 lines: one new<div x-show="...">block with the panel.NO backend change. NO JS change. Pure template addition because:
selectedItemalready gets the full API response (backlog.js:80)resolution_sha+resolution_noteare now inBacklogItemRead(PR feat(backlog): expose resolution_sha + resolution_note in API (#30) #3)Test
Visual verification on staging. Natural test cases:
resolution_sha=b50d48c)resolution_sha=70f166f)Both should show the new panel on their detail view.
Risk
Generated with Claude Code (Opus 4.7).