I can see a lock being useful for accidental modifications and deletions, but in terms of movement…
What should happen if you have 4 rules, lock the 2nd, and try to drag the 4th rule above the first?
Should the move…
Fail completely (because it passes over a locked rule)?
Stop at the point below the 2nd (because that’s where the first lock in its path occurs)?
Complete successfully overall (since neither the source or target are themselves locked)?
Whatever YOUR answer is, chances are the ideal would be different for everybody… Personally, I’d be in favor of either 1 or 2, but not 2, as the same “reflexes” that can cause you to delete a rule you didn’t mean to will make you move a rule to a place, and make you believe it’s moved correctly, though it’s moved, but not correctly.
Yeah. Definitely it is not easy. What about general lock locked by default automatically when user logs in? Or just confirmation popup when movement or deletion is invoked?
This is very good feature request, I thought i’m just the only one looking this as well i’m working with a home grown DIY zone firewall implementation and I this is best fit