I'd personally recommend and customize the datamodel to create this specific incident class, so specific permissions can be assigned.
I can confirm this. @dcoille Can you check whether this is now intended, or if it's a bug? The behavior most certainly changed.
You could consider hiding the field and setting a default value. This default value may be visible in certain lists though.
You're never really upgrade-safe I'm afraid. I'd base it on https://store.itophub.io/en_US/products/itop-portal-new-look-for-3.2-lts nowadays. Check https://github.com/Combodo/itop-portal-new-look-for-3.2-lts/tree/master -> datamodel to see some specific overrides. You can create your own extension that (1) requires this new portal, and (2) overrides the specific bit you'd like to keep changes minimal.
A new version of this extension is available now. It's rewritten to be future-proof; and contains some new features as well (e.g. multi selection in dashlets, the option to show/hide the search and filter options, or to add a description, ... ). Expect more features in the future; but you can already start mapping your objects and/or tickets! 😁 🌍 Remember: You can do this on a typical background map (such as OpenStreetMap); or on e.g. a floor plan you upload (both georeferenced and plain images are...
https://www.itophub.io/wiki/page?id=latest:install:requirements Seems iTop shouldn't have any issues with it?
I believe one of my prospects was a telephone company. Another was a VoIP Provider, but that's something different ;)
If you're familiar enough with PHP, you could dig into it. With Hybrid Auth (similar but different extension), the issue had to do with redirection and using the wrong HTTP referer at some point; if I remember correctly. I manually patched it for one of my customers; and reported it to Combodo.