Project

General

Profile

2.9

closed

01/31/2022

Additional improvements in Mentat 2.x series

100%

23 issues   (23 closed — 0 open)

Issues by
Bug

14/14
Feature

4/4
Support

1/1
Config

1/1
Task

3/3
Related issues
Bug #7106: Notification mails about new users for the group do not seem to go to group admin Actions
Bug #7215: Wrong usage of DB array in mentat_main/settings_reporting/emails Actions
Bug #7220: Erroneous values in mentat_main/reports_events/mail_to Actions
Bug #7365: Buildbot warnings on mentat-deb Actions
Bug #7377: Warnings by pyflakes on build Actions
Bug #7382: When daemons run in parallel, pid files are generated with wrong PID in name Actions
Bug #7449: Cancelling creation of network record results in internal server error Actions
Bug #7466: Viewing details of abuse group in reports/dashboard results in internal server error Actions
Bug #7501: IPv6 addresses are not shown in report details Actions
Bug #7507: menat-controller.py --command disable shows error Actions
Bug #7519: Cancel buttons are validating fields Actions
Bug #7542: mentat-controller.py not working with jinja2 version 3.0.1. Actions
Bug #7548: mentat-enricher.py error in Vagrant box Actions
Bug #7563: PassiveDNS REST API token displayed to user on connection error Actions
Feature #6227: Incorporate new info from Negistry into group db and reporting Actions
Feature #6255: Move attachments from emails to web Actions
Feature #7052: Link report to each group which owns it Actions
Feature #7257: Store email addresses to which the report was sent Actions
Support #7555: Upgrade PostgreSQL to v14 Actions
Config #7567: Update reporter templates to support different wording for severity Actions
Task #6205: Review encapsulation of SQLAlchemy and Psycopg2 DBALs Actions
Task #6239: Simplify/remove too detailed user settings for reporting Actions
Task #7041: Use Vagrant as alternative tool for local development Actions