Martin Hauser

Thanks again for digging into this, @alehaa. As you may know, I’m not a maintainer here, so this isn’t a decision - just my perspective. A minimal, opt‑in MPTT approach...

**Status: Draft** This PR is marked as a draft because it would currently conflict with the open PR **#275**. Once **#275** is merged into `dev`, I’ll rebase this branch on...

Thanks for the thoughtful request and for outlining the troubleshooting use case - very helpful context. I agree it’s reasonable to include **Access List (ACL) names** in global search and...

Quick update: I’ve implemented **item 2 (SearchIndex / Global Search coverage)** for the existing ACL and Rule models (no new comment field on Rules in this pass). The work is...

Thanks so much for the review and for testing, @alehaa. Really appreciate your time and care!

Thanks, @alehaa! A global configuration setting seems like the right first step. If there’s interest in per‑user control later, we can track that as a separate feature request. Are you...

Thanks for opening this issue — and for the clear screenshot. From what I can see, this looks like a side effect of how **“mark populated”** works on IP ranges....

Hi! Thanks for the report and the earlier analysis. This does look consistent with the bulk actions refactor. I’ve been experimenting with a possible fix, but I’m not 100% sure...

I’m happy to open a PR if it’s accepted.

**Additional reproduction using core `VLANGroupTest` (`ipam.tests.test_api`)** You can reproduce the same mismatch in NetBox core (so this isn’t plugin‑specific) by adding a single `vid_ranges` entry to the existing API test....