Skip to content

Hdpi 2983 build case details tab#1844

Open
gmmagruder wants to merge 52 commits into
HDPI-2978-summary-tabfrom
HDPI-2983-build-case-details-tab
Open

Hdpi 2983 build case details tab#1844
gmmagruder wants to merge 52 commits into
HDPI-2978-summary-tabfrom
HDPI-2983-build-case-details-tab

Conversation

@gmmagruder
Copy link
Copy Markdown
Contributor

@gmmagruder gmmagruder commented May 18, 2026

Jira link

See HDPI-2983

Change description

  • Add case details tab
  • Build case details view
  • Move reusable code from summery tab into separate builders

Testing done

Unit tests, manual testing on local and preview

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?

  • Yes
  • No

Checklist

  • commit messages are meaningful and follow good commit message guidelines
  • README and other documentation has been updated / added (if needed)
  • tests have been updated / new tests has been added (if needed)
  • Does this PR introduce a breaking change

gmmagruder added 30 commits May 11, 2026 21:10
…s-tab

# Conflicts:
#	src/main/java/uk/gov/hmcts/reform/pcs/ccd/CaseType.java
#	src/main/java/uk/gov/hmcts/reform/pcs/ccd/PCSCaseView.java
#	src/main/java/uk/gov/hmcts/reform/pcs/ccd/domain/PCSCase.java
#	src/main/java/uk/gov/hmcts/reform/pcs/ccd/view/CaseTabView.java
#	src/test/java/uk/gov/hmcts/reform/pcs/ccd/view/CaseTabViewTest.java
@gmmagruder gmmagruder marked this pull request as ready for review May 21, 2026 12:34
@gmmagruder gmmagruder requested review from a team as code owners May 21, 2026 12:34
@gmmagruder gmmagruder requested review from andrewdami11, benouaer and libanAbdirahman1 and removed request for a team May 21, 2026 12:35
.showCondition(ShowConditions.stateNotEquals(AWAITING_SUBMISSION_TO_HMCTS))
.field(PCSCase::getCaseFileView, null, "#ARGUMENT(CaseFileView)");

buildCaseDetailsTab(builder);
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

AC01 says the Case Details tab should appear between the parties tab and Case File View, so could we move the tab ordering around slightly to match that? happy to leave it with you.

Copy link
Copy Markdown
Contributor Author

@gmmagruder gmmagruder May 21, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Have shifted the order of the tabs to be parties, details, case file view, summary to be considered with figma

buildSuspensionOfRightToBuyTabDetails(pcsCase);
String dateSubmitted = formatSubmittedDate(pcsCase.getDateSubmitted());

CaseDetailsTab caseDetailsTab = CaseDetailsTab.builder()
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

AC02 says blank optional fields should show once a section has been started, but AC10 says sections should not show until answers are provided. At the moment some draft sections appear with only blank values, so the requirement may need clarifying. Should we only show a section once at least one relevant answer exists, then show blank optional fields within that section?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As I understand the requirement, sections should remain hidden until there is an answer to one of the sections. After this, the other tables within that section should appear (which may have blank answers if had not yet been answered)

Comment thread src/main/java/uk/gov/hmcts/reform/pcs/ccd/domain/tabs/details/CaseDetailsTab.java Outdated
Comment thread src/main/java/uk/gov/hmcts/reform/pcs/ccd/domain/tabs/details/CaseDetailsTab.java Outdated
@NoArgsConstructor
@AllArgsConstructor
public class UnderlesseeOrMortgageInformationTabDetails {

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you please double check the naming's compared to Figma

Copy link
Copy Markdown
Contributor Author

@gmmagruder gmmagruder May 21, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is a limitation here. I can't directly number them all and there can be more than one. I also tried to inherit AddressUK for the address but the CCD labels aren't inherited hence why addressKnown is just it's own row.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah yes that's fine, I meant for the of text name, Excel shows 'Underlessee or mortgagee 1’s name known?' so without the number, I think it should be 'Underlessee or mortgagee name known?' instead of 'Underlessee or mortgagee’s address for name known?'

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah yeah - I did catch that earlier but seems like it didn't get pushed. Now fixed.

@CCD(label = "Claimant type")
private String claimantType;

@CCD(label = "Claim against trespassers?")
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There seems to be a difference between Figma and Excel, Figma shows to have the label you already have and Excel says to have label 'Is your claim a trespass claim?'. I think it needs clarifying which one to follow

@hmcts-jenkins-j-to-z hmcts-jenkins-j-to-z Bot requested a deployment to preview May 21, 2026 14:55 Abandoned
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants