Skip to content

[SC-17292] Document risk tier assessment activity in the record Activity feed - #1443

Merged
juanmleng merged 2 commits into
mainfrom
juan/sc-17292/document-risk-tier-assessment-activity
Jul 30, 2026
Merged

[SC-17292] Document risk tier assessment activity in the record Activity feed#1443
juanmleng merged 2 commits into
mainfrom
juan/sc-17292/document-risk-tier-assessment-activity

Conversation

@juanmleng

@juanmleng juanmleng commented Jul 29, 2026

Copy link
Copy Markdown
Contributor

Pull Request Description

What and why?

Documents the risk tier assessment lifecycle events added to the record Activity feed by backend#3396 and frontend#2749 (SC-17292).

Before: the record Activity overview lists what the feed shows — fields, stage transitions, documents, test results, artifacts, comments, stakeholders, workflow activity — but not risk tier assessments, even though they now appear there as first-class events.

After: one bullet added for risk tier assessments created, updated, published, archived, versioned, or deleted.

Preview

How to test

  1. Open the preview link above and confirm the bullet reads "Risk tier assessments created, updated, published, archived, versioned, or deleted" between Stage transitions and Updates to documents.
  2. To check it against the product, publish or archive a risk tier assessment on an inventory record and open the record's Activity tab — the rows appear under both All and Model Updates.

What needs special review?

The edited file is a shared include. Besides the Activity guide it is also pulled into two training decks — site/training/common-slides/_track-changes-updates.qmd and site/training/common-slides/_view-record-activity.qmd — so the new bullet appears in those slides too. That is intended, but worth a look if slide length matters.

Wording note: the docs use "risk tier assessment", while the Activity rows themselves render as "Risk assessment <name> was published". The bullet follows the docs' terminology rather than the UI string.

Dependencies, breaking changes, and deployment notes

Release notes

The record Activity page now lists risk tier assessment activity — assessments created, updated, published, archived, versioned, or deleted — alongside the field, document, and workflow events it already showed. Learn more ...

Checklist

  • What and why
  • Screenshots or videos (Frontend)
  • How to test
  • What needs special review
  • Dependencies, breaking changes, and deployment notes
  • Labels applied
  • PR linked to Shortcut
  • Unit tests added (Backend)
  • Tested locally
  • Documentation updated (if required)
  • Environment variable additions/changes documented (if required)

The record Activity overview lists what the feed shows, but risk tier
assessments were missing even though they now appear there as
first-class events.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

Pull requests must include at least one of the required labels: internal, highlight, enhancement, bug, deprecation, documentation. Except for internal, pull requests must also include a description in the release notes section.

@juanmleng juanmleng self-assigned this Jul 29, 2026
@juanmleng juanmleng added the documentation Improvements or additions to documentation label Jul 29, 2026
@juanmleng
juanmleng requested review from cachafla, Copilot and emmavdh and removed request for Copilot July 29, 2026 19:43
@github-actions

Copy link
Copy Markdown
Contributor

Validate docs site

✓ INFO: A live preview of the docs site is available — Open the preview

@juanmleng
juanmleng added this pull request to the merge queue Jul 30, 2026
Merged via the queue into main with commit ae985b1 Jul 30, 2026
4 of 5 checks passed
@juanmleng
juanmleng deleted the juan/sc-17292/document-risk-tier-assessment-activity branch July 30, 2026 14:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants