2022.04.11
Bugfixes
- Fixed an issue where file uploads not related to markdown fields were broken.
- Fixed an issue where changing the client of an assessment would cause some tasks and notifications to throw an exception.
This release brings webhooks to Reporter for extra flexibility and extensibility! Webhooks are almost always faster than polling the API, and require less work on your end.
The following events are supported assessment:created, assessment:updated, finding:created, finding:updated and finding:published.
NO_AUTO_CREATE_USER exception when using Azure managed MySQL.This release dramatically improves the readability when writing your findings in the new context-aware editor of Reporter. The editor has many other improvements, such as a side-by-side feature that automatically updates the preview when writing your content.

Each assessment has a short ID. This is used to identify the assessment and the associated findings uniquely. It is now possible to use custom short IDs. Via the settings page, you can enable custom short IDs as the default.
DB_SERVER_VERSION setting.Previously, when a researcher selected a template to create a finding, the 'Template Suggestions-tab' showed templates attached to that specific section in the assessment type used. However, this relied on an admin user going over the sections of each assessment type and manually attaching templates.
This process is now automated. When a researcher creates a finding using a template, this template will be suggested for that section in other assessments of that type. Templates that are often used appear more prominent, also recently used templates are slightly more prioritized.
Is private is toggled and whether review status is set to published.
created_at field after severity. This is equivalent to sorting by number in an assessment context. The new sorting applies to the researcher panel, results lists, and the report. Findings on index pages are still sorted newest first, to avoid showing very old findings.Enter in global search no longer refreshes the page. The global search icon is now a loading icon while waiting for search results.Findings to Assessment Sections was incorrectly named section, which caused an exception when queried and caused the correct relation, assessmentSection to be unusable. business_impact and target_type fields are now correctly listed as integers in the API docs.company_phone_1 is not set.