AAT Siege Mode doesn't work with original keybinding

Product: Star Wars Battlefront II
Platform:PC
What is your issue related to? General
Summarize your bug Changing the keybind for the AAT's Siege Mode makes it so the ability cannot be used.
What is your gamertag/PSN ID/EA Account name? LemonLimeLife
How often does the bug occur? Every time (100%)
Can you tell us the date (MM/DD/YYYY) that you saw the bug? (08/04/2017) It's been there since beta and is still present.
What time did you see the bug? (HH:MM AM/PM) (12:00 am)
In what game mode did the bug occur? Galactic Assault
What is your time zone? CST - GMT - 6:00
Steps: How can we find the bug ourselves? Change the "upper ability" keybind to something other than the default "E" and attempt to use the Siege Mode ability on the AAT.
What happens when the bug occurs? Changing the keybind for the AAT's Siege Mode makes it so the ability cannot be used. You can still activate the ability with whatever keybind you've changed it to but once you toggle into Siege Mode you cannot pivot or fire the Siege cannon. Instead you are stuck in place and can shoot from the main side mounted blasters. You can only properly use Siege Mode if the keybind is the default "E". This bug doesn't appear to affect any other vehicles.
What do you expect to see? The AAT's Siege Mode ability should be able to be properly activated when pressing the assigned key.
Please select your region North America
AMD or Nvidia Model Number Nvidia Geforce GTX 1070

‌

Changing the keybind for the AAT's Siege Mode makes it so the ability cannot be used. You can still activate the ability with whatever keybind you've changed it to but once you toggle into Siege Mode you cannot pivot or fire the Siege cannon. Instead you are stuck in place and can shoot from the main side mounted blasters. You can only properly use Siege Mode if the keybind is the default "E". This bug doesn't appear to affect any other vehicles.

This is a problem for people like me who like to customize their controls.