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.
What does this do?
Why are we doing this? (with JIRA link)
Jira:
These come from the first round of QA testing. On dev the date fields were being display as
${day}-1
which is odd but we've changed to LocalDate in an attempt to resolve this. Note that they are stored in the db without a timezone and I'm not sure exactly where a tz is being implicitly added, but LocalDate does not have one so hopefully it will work as expected. If not we can handle the formatting in the query.The Inventory Consultation report was missing the inventory date which should have been included with the inventory status when present.
The Summary Consultation report needed to pull archaeological sites from the related CollectionObject's field collection sites.
There were also some copy/pasted column names which I've updated for each report so that the column names are consistent with the record type.
How should this be tested? Do these changes have associated tests?
Dependencies for merging? Releasing to production?
None
Has the application documentation been updated for these changes?
No
Did someone actually run this code to verify it works?
@mikejritter tested locally