ToDo before Release

[Tomas]

This list is no longer maintained!
Unimus 1.0.0 was released, and us such this old list is deprecated.

The ToDo list before Unimus leaves the Beta phase and enters Release.
(the list is in no particular order - priorities are not yet decided)

Please note that this list is in addition to solving all the known issues outlined here:
Known issues list

Release ToDo list:

• Notify when a newer version is available (both in UI and over email/push if configured)
• Database locking
• Finish logging (unify logging levels)
• Debian packages (includes having our own apt repo)

[Tomas]

This list contains features that were previously on the ToDo list, but were already implemented.

Implemented from ToDo list:

• PostgreSQL support
• User portal (license purchase/management)
• Finish UI redesign
• Mass device import 1 - paste a list of addresses, add all of them
• Mass device import 2 - .csv file with device addresses, descriptions
• Mass device import 3 - import from NetXMS
• Mass device import 4 - import from Zabbix
• Automatic database upgrade process
• After connection to database, check if the database encryption key is correct (verify by decrypting an encrypted static well known phrase and check if the result after decryption is as expected)
• Implement notifications
• Notification configuration screen (which events generate notifications)
• Windows installer (should install Unimus as a Windows Service)
• When user changes license key in config file, do not apply the change until user approves it in GUI (show proper warning on what effect changing the license key has)

[sleepingjake]

3 things that I've seen that I would like to see improved,

-Importing from the dude, specifically to select the ability to import only devices with routerOS ticked
-Setup process was a bit glitchy, I ended up having to redo mine twice
-ability to add additional logins

Otherwise I love what I'm seeing, the ability to compare a backup with a prior backup is great.

Thanks for all of your hard work!

[Tomas]

-Importing from the dude, specifically to select the ability to import only devices with routerOS ticked

This is rather problematic... Dude v3 uses a plaintext file for data storage, not event a database. Dude v4 uses a really old version of SQLite. I dont even know what the "new" Dude uses.
Sadly, Dude doesnt have any API either to use for communication.

-Setup process was a bit glitchy, I ended up having to redo mine twice

What exactly were the issues?
I would really like to know so I can fix them

-ability to add additional logins

This (together with Radius integration) will be coming in one of future patches.
(I have actually already started working on it)