Generate DOCX report broken for existing findings with empty affected entities about ghostwriter HOT 4 CLOSED

Hey @smcgu, as I mentioned in your other issue, it's best to use the code in main or the latest archive of the latest release. The v4.2 development branch is not ready for production use right now.

How did you load these findings into the database? If opening the finding and saving it without making any changes resolves the problem, that suggests the database entry is in a bad state with fields set to null that should never be null. When you save the finding, Ghostwriter fixes the bad fields by setting them to blank (not null). I can only reproduce this issue if I manually edit the database to null a field.

from ghostwriter.

These findings were added to the findings library, added to the report, and edited in the Ghostwriter web UI. They were added to the report weeks ago and edited within Ghostwriter. There was no manual manipulation of the report findings through scripted API calls and no direct access of the database.

As mentioned, the findings and report generation work fine with v4.1.0, but are broken after upgrading to the latest v4.2.0 on the v4-1-dev branch.

The only possible thing that I can think of is that a few days ago I performed a bulk export and import of the findings library. However, report generation still works fine on v4.1.0 and my very limited understanding is that this process should only affect the findings library not findings already added to reports and their affected entities fields.

from ghostwriter.

This issue has been labeled as stale because it has been open for 30 days with no activity.

from ghostwriter.

This issue is closed because it has been inactive for 14 days since being labeled stale. Feel free to re-open the issue with a comment. If this needs further discussion (e.g., a feature request), it might be better to open a topic under the Discussions tab.

from ghostwriter.