For safety reasons, I have suggestion: We have to click inside the tick box to change the state of a BOOL instead of anywhere in the value column. Or at least have the option to do so?
I selected the row above my INT to show this. If your mouse pointer is just inside the blue area when intending to click the INT, it sets the bool to true. Can cause unwanted things to happen. Read/Write of course, need to be enabled to change the INT.
Thoughts? 
You can put it in the ideas portal:
Here’s an exiting idea for adding a confirmation to Boolean tag click.
https://ideas.inductiveautomation.com/ignition-features-and-ideas/p/tag-browser-boolean-checkbox
Eeewwww! Please, no!
Yeah I don't like the confirmation either, but requiring a click on the actual checkbox instead of anywhere in that column seems reasonable.
Requiring the click on the actual checkbox would be a huge help.
I partially agree that adding a confirmation could get annoying pretty quickly, but the current “single click and it changed” is honestly pretty scary. One errant click and you just accidently changed a tag, and if it’s an OPC tag you just wrote a new value to a machine.
All the other tag types require multiple actions to edit - double click, make the change, and hit enter.
There is already a designer connection mode feature, that defaults to read-only, to catch errant writes from the designer.
The OP's formulation is a nice middle ground, and matches the behavior of real UI checkboxed that are bidirectionally bound to tags.
I'm on board with narrowing the click target to just the actual checkbox enough that I made it an actual feature ticket.
