Skip to content

v3.2.1 — a P1 use case between two P0 rows was promoted to P0

Choose a tag to compare

View all tags
@bpmforge bpmforge released this 05 Aug 19:56
· 91 commits to main since this release
v3.2.1
c825859

v3.2.1 — a P1 use case between two P0 rows was promoted to P0

validate-requirements-matrix.sh read priority with grep -A5, and a 5-line window in a UC index table reaches the next four rows — so any P0 neighbour promoted a P1/P2 case. Reported 18 P0 on a real 19-case catalog where the truth is 14, while validate-sequence-coverage.sh read the same file and said 14.

Priority now comes from the case's own row, or its own section bounded by the next heading. Never a window. Both validators agree at 14.

625 tests green.

Assets 2
Loading