Adding the ability to check all necessary compatibility settings of a .gwbk project that will be loaded into another gateway before the load would be incredibly useful. This way, the Ignition .conf file for the project will be able to be edited prior to restoring the backup, saving a lot of headache.

Enable a param to inser some Chromium Switches before create the Web Browser in the Vision module. Features in: https://jxbrowser.support.teamdev.com/support/solutions/articles/9000013080-chromium-switches

Currently have to use kepware's driver for Beckhoff PLC, and would be great to have a direct connection using a driver in Ignition

Gateway email messages (alerts for coding errors, etc) do not have an option for STARTTLS or other encryption like other email messages have. Please allow encrypted gateway email messages.

For large enterprises, the load on domain controllers can be heavy when searching through large OUs. Could you create a user source that would ask for the role(s) required to log in, then cache all the users with that role(s)? Then a search for all users would not be required. I assume this might increase the work for the Ignition server and decrease the work for the DC... Choosing this user source would be an implementation decision for the SI.

logback.xml is not included in the backup file, but should be since it can be customized and (potentially) affect the actions of a restored system. (see ticket #92453)

Would function just like system.gui.getQuality, but for tags. Would return an integer value of the tag's quality. Simply reading a tags.quality attribute returns a DataQuality type value, which is hard to convert to a string or integer. (or at least I can't figure it out)

A problem we're seeing with Ignition's AD authentication is an inability for a user to see when their password is expiring and they're unable to change their password should it expire! This is a big problem where users typically only use a HMI and are not required to use a PC for any other duties. Users could be left in a position where they can't login when there is no support on site to advise why they can't login! Most 21 CFR 11/Annex 11 compliant software packages we use allow these features,.

It's kind of annoying to have to click it on for every object, and I don't see why anyone would't want to have it turned on. It just looks better.

It would be awesome if we could get breakpoints, variable inspection and step over / step into features.