release: glossary admin — last change, field descriptions, active portfolios and a safer merge - #205
Merged
Merged
Conversation
…elds Requested for the glossary admin panel on 2026-09-15: - A "Last change" column: who changed each record last and when. The admin DTO gains `last_modified_at` and `last_modified_by` (additive; the public `GET api/glossary` is untouched). Authors are resolved in one query for the whole list; an id that matches no user leaves the cell as "Unknown user". - A description of what Active and Inactive mean, on the Status header and tag. - A description of "Show in dashboard": it only adds the term to `GET api/glossary/dashboard` and does not change the public glossary page. - Portfolio pickers offer only active portfolios. A closed portfolio a term is already linked to stays in its edit dialog, so saving never drops the link. - `mergeInto` refuses an inactive target. The panel already hid the button; a direct call could move portfolios onto a hidden row with no error. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
…eld-help feat(glossary-admin): show who changed each term, explain Active/Inactive and dashboard, offer only active portfolios
|
SantiagoSC1999
approved these changes
Sep 16, 2026
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
2 participants
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.
Promotes to production the glossary admin adjustments requested on 2026-09-15 — Jira CLR-56. Two commits, front and back only, no migrations (38 → 38).
What changes, for whoever uses the panel
GET api/glossary; an inactive one is hidden from both, and nothing is deleted.GET api/glossary/dashboard; the public glossary page is not affected.(closed), so saving never drops the link.409), also from a direct API call. Raised in the review of release: glossary versioning per portfolio, expired sessions that log out, and the visual revamp #201: the panel hid the button, but the endpoint did not.Contract
GET api/glossaryandGET api/glossary/dashboardare unchanged. The admin endpoints gain two keys per term (last_modified_at,last_modified_by) and lose nothing.Verification
staging.api/glossary,/dashboardanswering 200, admin endpoints still 401 without a token.Not covered
updated_byshows its creator as the last change.🤖 Generated with Claude Code