Jira Align to use Server time for all timestamp date fields in its database.

We recently worked on a issue that revealed the timestamp date fields in JA database
use GMT 0 as standard timezone while the timestamps for the updates on Work Items use server timezone, making usability of the data in Enterprise Insights very confusing.

This behavior is across Jira Align for all work items in multiple History/Audit tables.

E.g. Whenever a Feature has its status changed, the specific field for that status will be updated with the Server timestamp, while the history record of that update will get the GMT 0 timestamp, making it  confusing to understand when the record was really updated.

Steps to Reproduce

Here I will share a SQL query and result to better understand the behavior, where the fields ValidFrom and ValidTo will record the GMT 0 timestamp and pendingapprovaldate field will record the Server timezone.

With any existing work item in Jira Align run the following query

select
    fh._ValidFrom,
    fh._ValidTo,
    fh.pendingapprovaldate,
    fh.PendingApprovalDateEnd,
from AgileCraft_ABCCORP.dbo.tblRequestsAudit fh
where fh.Requestid =1200

Results of the query:

_ValidFrom |._ValidTo. | pendingapprovaldate | PendingApprovalDateEnd |
2023-04-17 17:38:25.250 | 2023-04-17 17:39:32.987 | 2023-04-17 14:38:25.000 | NULL | 

You can see the difference in the timestamps from the first column, where Jira Align is recording the status update on the database, to the third column, where Jira Align keeps the server time when the update was made to the record. The first column is using GMT 0 (17:38:25.250) and in the third column it is using the Server timezone (14:38:25.000)

Expected Results:
Have both fields with the same Date and Time timezones