[ElizabethWhyman]

Reported in panoramicdata/PanoramicData.Skills#1910.

Problem

The built-in ticket-quality rubric capped every MS ticket at 79 (GOOD) when Release Notes was empty, whatever its status. A ticket in Ready for Progress could never reach EXCELLENT, even though release notes cannot be written before the work is done. Fix Version was already status-aware; Release Notes was not. Observed on MS-27963.

Change

• New named condition releaseNotesDue, a reference to contractEvidenceDue (Ready for Test onwards), so the two MS status gates cannot drift apart.
• ReleaseNotes and EpicReleaseNotes: before Ready for Test an empty field scores 100 with ○ Release Notes: Not required yet (status: ...).
• The Release notes mandatory cap applies only from Ready for Test onwards. Notes already written earlier are still checked and their findings reported, but do not cap.

The Skills Send to test readiness gate scores with -AsStatus 'Ready for Test', so it still refuses a ticket with no release notes.

Tests

ReleaseNotesAssessmentTests now defaults to Ready for Test, and adds cases for empty notes before Ready for Test (Improvement and Epic), flawed notes before Ready for Test (reported, no cap), and empty notes at In Test and Closed (cap). All 999 tests pass; the four new cases fail against the previous rubric.

After merge

Release the package, then bump the pin in PanoramicData.Skills _common/IssueQuality.cs and Magic Suite's Directory.Packages.props.

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 complexity · 0 duplication

Metric	Results
Complexity	0
Duplication	0

View in Codacy

AI Reviewer: run a review on demand. To trigger the first review automatically, go to your organization or repository integration settings. AI can make mistakes. Always validate suggestions.

_{TIP This summary will be updated as you push new changes.}