Note this update may take a little longer to complete than usual. Grab a ☕, and enjoy this last update of 2022 🍾
Timezones
Users can now configure their timezone. The user's timezone will be automatically set when the user first logs in after this update and can be changed from the user's profile. Users will see timestamps according to their local time, except in generated files such as PDF reports. Generated files use the application's timezone.
The application timezone can be configured via the Settings > General > Functionality page.
Reports
Any timestamps on reports, such as those in finding metadata and the generated_at placeholder you may have on the front page, are reported in the application's timezone. If you want to display the current timezone on the report, there are two options:
- If you have a
generated_attimestamp on the front page of the report, we recommend adding the timezone to the format string. EitherTfor timezone orOfor the difference to GMT. See https://www.php.net/manual/en/datetime.format.php under timezones for more options. See Settings > Report Text Boxes. For example, you can change the default[[GENERATED_AT|Y-m-d H:i:s]]to[[GENERATED_AT|Y-m-d H:i:s T]]to add your timezone at the end. - Alternatively, you can use a placeholder component in an assessment section to add the timezone elsewhere in the report. Either by name (e.g., CET) or by difference to GMT (e.g., +0100). Use the
+button when editing a section, selectPlaceholderand choose one of the timezone options.
API Changes
- All timestamps returned by the API are now in an ISO8601-compatible format, e.g.,
2022-12-18T16:47:56.000000Z. - Any timestamps posted to the API now expect an ISO8601-compatible format (currently only
found_at).
Improvements
- More context about each finding is now displayed when importing findings from previous assessments, including the finding's status, severity, and the original assessment section.
- The severity legend is now also shown in the findings tab on the assessment page.