Allow Mission Time Zone Modification After Asset Assignment

We encountered a scenario where an asset had been relocated from one time zone to another, but Flight Vector continued to display the asset's previous location and associated time zone. The dispatcher was unaware of this discrepancy when assigning the asset to a mission.

As a result, the missions request times were created using the incorrect time zone. When the dispatcher later attempted to close out the mission, all timestamps remained in the wrong time zone. There was no available option to update the mission Request times to the correct time zone after the asset had been assigned.

We are requesting the ability for users to modify a mission's time zone after asset assignment. This would provide a mechanism to correct situations where an asset's configured or displayed time zone does not reflect its actual operating location at the time of the mission.