API Filtering
In the previous release, we introduced new API filter operators such as greater-than and not-equal. A bug in that implementation caused some API integrations to break when multiple filter values were used. Previously, a filter like filter[severity]=1,2 returned results where severity = 1 OR severity = 2. Due to the bug, this was incorrectly evaluated as severity = 1 AND severity = 2, resulting in no matches. This issue has now been fixed. Multiple filter values once again default to OR behavior.
In addition to this fix, we added support for more advanced filtering. Filters prefixed with and_ require all conditions to be met, enabling use cases such as “not 1 AND not 2.” For example: filter[and_severity]=<>1,<>2.
Other Improvements
- Improved several UI interactions with checklists:
- You can now collapse categories while filtering.
- You can now stop editing test cases by clicking on them.
- Test case finding link now has a visual indicator that findings are a link.
- Those finding links now open in a new tab.
- When the checklist is updated, test cases you are editing no longer reload.
Bug Fixes
- Fixed unreliable syncing to Elasticsearch, causing some or all results to be missing from search results.
- Fixed the "Add Target" button in the targets tab on the main assessment page.
- Fixed a bug where non-markdown text fields, such as names and titles, that allow Todo tags, were saved HTML-encoded.
- Fixed an issue where Elasticsearch would reindex every night for large databases.
- Requesting a revision without text now correctly displays the validation error instead of reloading the page.
- Tables in PDF reports no longer sometimes run off the page if there is a placeholder in them.