Hi.
Is this the ToDo list currently in effect?
https://svn.netxms.org/public/netxms/trunk/TODO
Best regards.
Hi!
No, it isn't. Actually I don't touch this file for years. Many of featrures listed in that file already implemented, but some really important still not :( Currently I maintain my ToDo in internal Jira. Current list of open issues scheduled for 1.2.0 release looks like this:
Bug
[NX-75] - Button "Test" is not working on DCI transformation property page
[NX-80] - Reports not working on Windows
[NX-89] - Cannot delete non-existent object from event processing policy
Improvement
[NX-3] - Ability to set native agent port on node creation
[NX-4] - Add support for INFORM messages in trap receiver
[NX-7] - Apply policy to node by clicking on node and selecting policies from list
[NX-18] - Improve dashboard configuration tools
[NX-57] - Add certificate authentication to Java console
[NX-85] - Implement drop column functionality for SQLite
[NX-87] - Add web interface to WIndows installer
New Feature
[NX-2] - Autodiscovery: user should be able to set default settings for discovered nodes (e.g. no agent, no snmp)
[NX-5] - automatically create ChildStatus DCI when Network Service object created for Node
[NX-10] - Use Spanning Tree data for network discovery
[NX-33] - Implement configuration export in Java console
[NX-35] - Implement concept of "normal" interface state
[NX-38] - Add additional page for containers where threshold violations for underlying nodes are shown
[NX-43] - Allow per-DCI SNMP version settings
[NX-50] - Add possibility to add parameters and/or specify entry point in scripts called via %[] macro
[NX-51] - Ability to copy/paste scripts in script library
[NX-63] - Timed alarm acknowledgement
[NX-71] - Add new policy type for distributing log parsers
[NX-88] - Implement data export from log viewer
[NX-90] - Implement alarm comments
Best regards,
Victor
Hi Victor.
Okay, thanks for the info.
So, the next version release will be 1.2.0?
Best regards.
Yes, I plan that next release will be 1.2.0. Current 1.1.x branch is stable enough to consider it new production version and drop 1.0.x branch.
Best regards,
Victor