Import History: Make the absence of action more clear

[Maffooch]

In the event an empty report is submitted, and there are no findings to be closed, the test_import_finding_action_set will be empty. When viewing import history objects, there is no indication as to what occurred.

[sc-9738]

[dryrunsecurity]

DryRun Security Summary

The pull request involves a minor enhancement to the view_test.html template, adding an empty block to the finding_action_list loop to display a message when no findings are created, closed, or modified during import, without introducing any security concerns.

Expand for full summary

Summary:

The code changes in this pull request appear to be a minor enhancement to the existing functionality of the view_test.html template in the dojo application. The changes include adding an empty block to the finding_action_list loop in the import history section, which will display a message if there were no findings created, closed, or modified during the import. From an application security perspective, this change does not introduce any obvious security concerns, as it seems to be focused on improving the user experience by providing more informative messages to the user. Overall, this change does not raise any immediate security red flags.

Files Changed:

• dojo/templates/dojo/view_test.html: The changes in this file add an empty block to the finding_action_list loop in the import history section. This will display a message to the user if there were no findings created, closed, or modified during the import. This change is a minor enhancement to the existing functionality and does not introduce any apparent security vulnerabilities.

Code Analysis

We ran 9 analyzers against 1 file and 0 analyzers had findings. 9 analyzers had no findings.

View PR in the DryRun Dashboard.

[mtesauro]

Approved