Regression/Bug fixes in Oracle html report due to recent refactoring #2248
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.
Describe the changes in this pull request
Assigning empty value to Impact column for Oracle assessment report
Populate Issue Type for Oracle unsupported object type cases
https://yugabyte.atlassian.net/browse/DB-15035
https://yugabyte.atlassian.net/browse/DB-15037
Describe if there are any user-facing changes
NA
How was this pull request tested?
Manually verified the case.
Existing tests are enough, but need to be updated to check the assessment issue field to avoid these issue.
Does your PR have changes that can cause upgrade issues?