Repository navigation
MS release-notes and Ticket Contract assessments; justified not-needed tiers - #6
Merged
Merged
Conversation
Adds the fieldsDiffer condition, the isMs and isUndelivered named conditions, a ReleaseNotes assessment (EpicReleaseNotes for epics, since assessment names must be unique) weighted 6, and a mandatory 'Release notes' cap at 0.79. Not applicable outside MS and when resolution is set and not Fixed or Done. BuiltInRubricParityTests: no expectation changed. The Yoda fixtures with MS keys would now gain the new finding and cap, so the parity rubric drops the ReleaseNotes assessments and cap, as it already drops Presentation; ReleaseNotesAssessmentTests covers them. A 1.1.6 rubric copy is a test fixture for the OPS unchanged-score test.
Adds the criteriaClassification measure (items, unclassified, must under a section), the contractEvidenceDue condition, a TicketContract assessment weighted 6 for MS non-epic delivered tickets, and a mandatory 'Ticket contract' cap at 0.79. From Ready for Test on, a Verification Evidence section with a Criterion table, Reachability, Not covered and a Suggested QA route is required. BuiltInRubricParityTests: no expectation changed; the parity rubric also drops TicketContract and its cap.
No Yoda parity fixture contains a matching line, so no parity score changes.
Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
…ntract Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…omer Both statuses follow In Test in the MS workflow, so a ticket in either needed no evidence. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A criterion is classified when it starts with MUST, SHOULD or MAY, contains exactly one distinct keyword, or is a list item under a label line such as *MUST* or MUST: (scope ends at the next label or wiki heading). Items mixing keywords without a leading one stay unclassified. Covers the MS-27557 and MS-27609 forms. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
NBGV appends the git height, so 1.2.0 is never published. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ng blocks Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Up to standards ✅🟢 Issues
|
| Metric | Results |
|---|---|
| Complexity | 115 |
| Duplication | 0 |
🟢 Coverage 98.18% diff coverage · -0.05% coverage variation
Metric Results Coverage variation ✅ -0.05% coverage variation (-1.00%) Diff coverage ✅ 98.18% diff coverage Coverage variation details
Coverable lines Covered lines Coverage Common ancestor commit (64e9691) 2005 2004 99.95% Head commit (7c8aaa3) 2057 (+52) 2055 (+51) 99.90% (-0.05%) Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch:
<coverage of head commit> - <coverage of common ancestor commit>Diff coverage details
Coverable lines Covered lines Diff coverage Pull request (#6) 55 54 98.18% Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified:
<covered lines added or modified>/<coverable lines added or modified> * 100%
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.
…limits Co-Authored-By: Claude Opus 5.5 <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
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.
Adds the MS ticket-readiness checks used by the Jira skill, the QA Dashboard and the Magic Suite release gate. Tracks #5 and Jira MS-27629.
What changes
NormalizedIssuegainsReleaseNotes(Jiracustomfield_10600, string or ADF) andResolution(fields.resolution.name); JSON keysreleaseNotes,resolution.ReleaseNotes(andEpicReleaseNotesfor epics), mandatory cap 0.79: present, not a placeholder, not generic, at least 8 words, differs from the summary, customer-facing (no ticket keys, paths or code identifiers; standards ids such as UTF-8 and CVE ids allowed), no em dash, British spelling.TicketContract(non-epics), mandatory cap 0.79: every acceptance criterion classified MUST/SHOULD/MAY (leading keyword, a single RFC 2119 keyword in the sentence, or a label line above), at least one MUST; from Ready for Test onwards (including Ready for Customer and With Customer) anh2. Verification Evidencesection, optionally(Retrospective), with criterion table, Reachability, Not covered and a suggested QA route.No documentation change: <reason>/No certification question: <reason>line.fieldsDiffercondition,criteriaClassificationmeasure.Evidence