Subnet matrix is no longer helpful when no scopes have been defined
Bug #1544059 reported by
Morten Brekkevold
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Network Administration Visualized |
Fix Released
|
High
|
John-Magne Bredal | ||
Bug Description
Once upon a shiny time, the subnet matrix would at least tell the user to add network scopes under SeedDB if there were none.
In NAV 4.4, it only says "Select scope you want to see the subnet matrix for", but displays no selection options and no course of action for the now bewildered user.
Suggested solution: As before, tell the user there are no configured scopes, and offer a link to SeedDB to add one.
Revision history for this message
| John-Magne Bredal (john-m-bredal) wrote | #1 |
| Changed in nav: | |
| status: | Confirmed → Fix Committed |
| Changed in nav: | |
| milestone: | none → 4.4.3 |
| Changed in nav: | |
| status: | Fix Committed → Won't Fix |
| status: | Won't Fix → Fix Released |
To post a comment you must log in.
Fix here:
https:/