tasklist2006
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
tasklist2006 [2007/05/11 10:53] jodal |
tasklist2006 [2007/05/11 13:32] jodal Moved to devel. |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Task List 2006 ====== | ||
| This document lists in more detail than the release notes tasks done in 2006 and January 2007 for **NAV 3.2** | This document lists in more detail than the release notes tasks done in 2006 and January 2007 for **NAV 3.2** | ||
| - | |||
| - | [[TableOfContents]] | ||
| - | |||
| - | |||
| - | |||
| - | ------- | ||
| Line 19: | Line 14: | ||
| * (//Fixed by mortenv//) Store the complete interface description string for router ports untouched in NAVdb. Modify the gwport report. | * (//Fixed by mortenv//) Store the complete interface description string for router ports untouched in NAVdb. Modify the gwport report. | ||
| - | |||
| - | ------- | ||
| Line 180: | Line 173: | ||
| * The maintenance list of NAV 3.1 is perhaps the least intuitive NAV page. Change this to a maintenance schedule page with a general calender month view. At each date the maintenance description is shown allong with the start (and end?) time for the maintenance window. The entries are in turn linked to a complete view of the maintenance task. If a room and/or location is on maintenance do not show the content of the room, but link to the report tool for details. | * The maintenance list of NAV 3.1 is perhaps the least intuitive NAV page. Change this to a maintenance schedule page with a general calender month view. At each date the maintenance description is shown allong with the start (and end?) time for the maintenance window. The entries are in turn linked to a complete view of the maintenance task. If a room and/or location is on maintenance do not show the content of the room, but link to the report tool for details. | ||
| - | |||
| - | ------- | ||
| Line 233: | Line 224: | ||
| Feel free to improve this view. A matrix that shows the grid lines would be better. Or take a look at how | Feel free to improve this view. A matrix that shows the grid lines would be better. Or take a look at how | ||
| Hobbit does this. I.e. use green and red balls/bullets instead, and drop the suggested grid lines. | Hobbit does this. I.e. use green and red balls/bullets instead, and drop the suggested grid lines. | ||
| - | |||
| - | ------- | ||
| Line 262: | Line 251: | ||
| * (Fixed by Morten) The room report uses netbox2, not netbox. Why??? See if netbox2 can be removed. | * (Fixed by Morten) The room report uses netbox2, not netbox. Why??? See if netbox2 can be removed. | ||
| - | |||
| - | |||
| - | ------- | ||
| Line 308: | Line 294: | ||
| * (//Fixed by jodal//) Remove the possibility of editing static routes in editDB (leaving the only nettypes to edit: reserved and scope) | * (//Fixed by jodal//) Remove the possibility of editing static routes in editDB (leaving the only nettypes to edit: reserved and scope) | ||
| - | |||
| - | |||
| - | ------- | ||
| Line 325: | Line 308: | ||
| * (//Fixed by jodal//) Info text explaining ARP and CAM timeouts. | * (//Fixed by jodal//) Info text explaining ARP and CAM timeouts. | ||
| - | |||
| - | |||
| - | ------- | ||
| Line 345: | Line 325: | ||
| * (Fixed by John Magne) Improve the data in the cricket menu column "description" | * (Fixed by John Magne) Improve the data in the cricket menu column "description" | ||
| - | |||
| - | |||
| - | |||
| - | ------- | ||
| ===== T9: Make a ranked statistics tool ===== | ===== T9: Make a ranked statistics tool ===== | ||
| Line 364: | Line 340: | ||
| * octets/errors for ports all/one switch/router | * octets/errors for ports all/one switch/router | ||
| * cpu load / memory usage for routers | * cpu load / memory usage for routers | ||
| - | |||
| - | ------- | ||
| Line 386: | Line 360: | ||
| * Complement the solution with an alert profiles page that lists the logged in user's sent SMSes. This gives the user the ability to check which sms'es that is (read: should be) sent him. Note: This webpage is present in NAV v2. | * Complement the solution with an alert profiles page that lists the logged in user's sent SMSes. This gives the user the ability to check which sms'es that is (read: should be) sent him. Note: This webpage is present in NAV v2. | ||
| - | |||
| - | |||
| - | |||
| Line 401: | Line 372: | ||
| * Include an about page i NAV 3.2 that give information about NAV, gives credit to all contributors, links to !SourceForge and metanav and perhaps encourages NAV users to send us a postcard. | * Include an about page i NAV 3.2 that give information about NAV, gives credit to all contributors, links to !SourceForge and metanav and perhaps encourages NAV users to send us a postcard. | ||
| - | |||
| - | |||
| - | |||
Page Tools
