- QUADS version (quads-2.2.4-20251106.noarch):
- Python version: 3.13.7
- Operating System: F42
Describe the bug
When you view the list of VLANs in the web UI on: https://quads_host/vlans
and you compare against: https://quads_host/api/v3/vlans/free
If there is a future scheduled allocation that is not current, then the VLAN will appear in the web UI, but will not be listed as available in the API.
A possible way to avoid the confusion in the disparity between the two sources of data would be to have the web UI list the future owner / ticket / cloud allocation (perhaps with an asterisk (*) marker to indicate it has not started yet. Furthermore, it would be nice to have the ticket numbers link to the issue tracking system, much as they do in the /assignments page.
Describe the bug
When you view the list of VLANs in the web UI on: https://quads_host/vlans
and you compare against: https://quads_host/api/v3/vlans/free
If there is a future scheduled allocation that is not current, then the VLAN will appear in the web UI, but will not be listed as available in the API.
A possible way to avoid the confusion in the disparity between the two sources of data would be to have the web UI list the future owner / ticket / cloud allocation (perhaps with an asterisk (*) marker to indicate it has not started yet. Furthermore, it would be nice to have the ticket numbers link to the issue tracking system, much as they do in the /assignments page.