Renaming of possessions case type. - #5333
Open
anthonydummer wants to merge 2 commits into
Open
Conversation
anthonydummer
requested review from
Josh-HMCTS,
balajisridharanhmcts and
olusegz07
July 28, 2026 15:07
Josh-HMCTS
approved these changes
Jul 28, 2026
RiteshHMCTS
approved these changes
Jul 29, 2026
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
3 participants
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
https://tools.hmcts.net/jira/browse/POFCC-370
Change description
When setting up the work allocation test configs, the short name was used in error when populating the caseType. This fix is to update the caeTypes defined in the file with the correct value.
Dependency PRs
The config change has been applied onto this pr. This is the work allocation enablement pr with this config applied and will allow possessions to test the fix.
#5334
Testing done
A temporary pr has been created where this will be tested against in order to allow the change to be tested against the possessions preview databases.
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