Hdpi 7368 - #2379
Open
gergelykisshmcts wants to merge 65 commits into
Open
Conversation
…e else with a migration already applied: master had reached V006, and this branch's migration was V004, so two V004s would have collided and made Flyway refuse to start. Renamed mine to V007__add_case_flag_visibility.sql. Full unit, checkstyle and DB integration runs are green post-merge, and the regenerated definition still shows both v2.1 display context parameters and all ten pre-condition states.
DB breaking change scanRecommended reading: HMCTS zero-downtime database deployments No potentially breaking database changes were detected in the changed Flyway migration This check only scans changed Run details: https://github.com/hmcts/pcs-api/actions/runs/32510006855?check_suite_focus=true |
CCD diff summary👉 Full report: https://github.com/hmcts/pcs-api/actions/runs/32946726487?check_suite_focus=true AuthorisationCaseState.json
CaseField.json
AuthorisationCaseEvent/AuthorisationCaseEvent.json
AuthorisationCaseField/wlu-team-leader.json
AuthorisationCaseField/wlu-admin.json
AuthorisationCaseField/leadership-judge.json
AuthorisationCaseField/judge.json
AuthorisationCaseField/hearing-centre-team-leader.json
AuthorisationCaseField/hearing-centre-admin.json
AuthorisationCaseField/fee-paid-judge.json
AuthorisationCaseField/ctsc.json
AuthorisationCaseField/ctsc-team-leader.json
AuthorisationCaseField/citizen.json
AuthorisationCaseField/circuit-judge.json
AuthorisationCaseField/caseworker-pcs-solicitor.json
AuthorisationCaseField/DEFENDANTSOLICITOR.json
AuthorisationCaseField/DEFENDANT.json
AuthorisationCaseField/CLAIMANTSOLICITOR.json
CaseEvent/requestSupport.json
CaseEvent/manageSupport.json
ComplexTypes/4_Party.json
ComplexTypes/PartySupport.json
CaseEventToFields/requestSupport.json
CaseEventToFields/manageSupport.json
CaseTypeTab/93_supportcitizen.json
CaseTypeTab/92_supportcaseworker-pcs-solicitor.json
CaseTypeTab/91_support[DEFENDANT].json
|
linusnorton
reviewed
Aug 10, 2026
tvr-hmcts
reviewed
Aug 10, 2026
tvr-hmcts
left a comment
Contributor
There was a problem hiding this comment.
This is looking cool. I've added some comments over missing path tests mainly.
# Conflicts: # src/main/java/uk/gov/hmcts/reform/pcs/ccd/PCSCaseView.java # src/test/java/uk/gov/hmcts/reform/pcs/ccd/PCSCaseViewTest.java
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.
Jira link
See HDPI-7368
Change description
Adds the Case Flags v2.1 Request Support and Manage Support journeys for external users in Manage Cases.
External users can view external support flags across the case, while creating and managing support is restricted to their own party or side.
Claimant and defendant parties are supported. The previous defendant-only behaviour in the internal Case Flags journey has also been corrected so claimant support can be recorded by internal users.
Added a separate external party support model so the external journey only exposes the support data it needs and does not expose the internal Party model or internal-only flags.
Updated party flag mapping to use party IDs rather than collection order.
Added organisation-name handling for organisation claimants.
Added validation for malformed or unknown party IDs.
Added hearing centre admin and team leader history visibility for the new events.
Separated the internal Case Flags update path from the external support update path so the two flag collections cannot overwrite each other.
Removed unused external event configuration and renamed the new external flag field to reflect that it applies to parties rather than defendants only.
Includes database and CCD configuration updates.
IMPORTANT: the PR BUILDS ON #2335 branch not yet in master!
Testing done
Unit tests and integration tests pass.
checkstyleMain and checkstyleTest pass.
Security Vulnerability Assessment
Checklist
PCS checklist
@EnabledIfEnvironmentVariable(named = "CCD_ENABLED", ...)+ shutter guard) unless they must run on unlabelled PRs (HDPI-8084)