Observations Tab about ghostwriter HOT 3 CLOSED

Hey @caderob, it looks like you're trying to reference observationday as a foreign key on the Observation table. You'd have to add your observationday table to the database and create a foreign key field on the Observation table. If this is meant to be the date you added the observation to the report, you can add a timestamp field that tracks that.

To group by day like findings are grouped by severity, you'd also need to create a custom filter like the one used for findings (e.g., group_by_severity). You need the equivalent of this for sorting by "observation day":

            {% group_by_severity report.reportfindinglink_set.all as severity_groups %}
            {% for group, values in severity_groups.items %}

As for the DREAD scoring, the built-in calculator uses CVSS v3 for now. There is a PR in progress to add CVSS v4. DREAD isn't planned, but I'd consider a PR for it if someone had the time to add it.

from ghostwriter.

Thanks for the input! I added 'observation_day' to the Observation table and I can see it has a 'null' value when I export my report to json, so that worked!

Now, I'm trying to update the front end Observation form to allow the user to enter the Observation Date before or after the Observation Description in a date format way like the image attached.

Could you help me figure out which file/s to amend to add an additional date field on the front end under each Observation?

Thanks!

from ghostwriter.

Take a look at the other forms with date fields. You can copy one of those, like the start date field configuration from the project form. You'll add your new date field to the observation form.

from ghostwriter.