HDPI-5157: Screen Updates: Display case data claim issued date#1975
HDPI-5157: Screen Updates: Display case data claim issued date#1975arun-hmcts wants to merge 11 commits into
Conversation
CCD diff summary👉 Full report: https://github.com/hmcts/pcs-api/actions/runs/28105403447?check_suite_focus=true No change |
There was a problem hiding this comment.
Current master only calls searchCriteriaIndexer.buildSearchCriteria(pcsCase) when the case type is not suffixed, but this branch appears to call it unconditionally. That looks unrelated to the ticket and could accidentally reintroduce global_search indexing for suffixed case types.
| .orElse(null); | ||
| } | ||
|
|
||
| private LocalDateTime getClaimIssuedDate(PcsCaseEntity pcsCaseEntity) { |
There was a problem hiding this comment.
Can we confirm the agreed CCD/frontend contract is root-level dateIssued rather than exposing/using possession_claim.claim_issued_date directly?
This is probably fine, but worth asking because the AC wording is explicit about possession_claim.claim_issued_date, while this creates a root-level dateIssued.
…rney
Jira link
HDPI-5157
Change description
HDPI-5157: Display case data claim issued date — Surfaces the claim's issued date from the claim entity through the start-event callback, exposing it as a new dateIssued
field on PCSCase (with ClaimantAccess/DefendantAccess) for pcs-frontend to read.
Field named dateIssued for consistency with the existing dateSubmitted and to align with PR #1934, backed by unit tests covering the populated and no-claims cases.
Testing done
Security Vulnerability Assessment
CVE Suppression: Are there any CVEs present in the codebase (either newly introduced or pre-existing) that are being intentionally suppressed or ignored by this commit?
Checklist