CIV-15269 Make dates mandatory sdo #4819
Merged
Conversation
This file contains 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
drummondjm
requested review from
ruban72 and
paulridout
and removed request for
a team
drummondjm
force-pushed
the
CIV-15269-hearing-date-sdo
branch
from
7cca58a
to
5c126b7
Compare
drummondjm
added a commit
that referenced
this pull request
Sep 23, 2024
Make dates mandatory so are/have to be pulled into document
drummondjm
added a commit
that referenced
this pull request
Sep 24, 2024
Make dates mandatory so are/have to be pulled into document
vasudevganesanhmcts
pushed a commit
that referenced
this pull request
Sep 27, 2024
* Changed spelling of Judgement * CIV-15269 Make dates mandatory sdo (#4819) Make dates mandatory so are/have to be pulled into document
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.
https://tools.hmcts.net/jira/browse/CIV-15269
Make date field mandatory for SDO, so no blanks in document
Does this PR introduce a breaking change? (check one with "x")