Issue Summary

Time stamps for Assignment Start Date in Feature Table (tblRequests) and Feature Process Step Assignment History report their time stamps for state changes in a mix of UTC and server time. The dates flow into Enterprise Insights where the issue is visible.

This is reproducible on Data Center: (yes)

Steps to Reproduce

1. Initiate a state change in a feature via process steps
2. Run this query after etl completes:

select [Feature ID],[Developmental Step] as 'Process Step',
GREATEST([Date Pending Approval],[Date Ready To Start],[Date Dev Complete],[Date In Progress],[Date Dev Complete],[Date Test Complete],[Date Accepted]) as 'Assignment Start Date',
'9999-12-31 00:00:00.000' as 'DateAssignment End Date'
from [current_dw].[Feature]
where [Feature ID] >= 5997
UNION
select [FK Feature ID] as 'Feature ID',[Process Step Name],[Assignment Start Date],[Assignment End Date]
from [current_dw].[Feature Process Step Assignment History]
LEFT JOIN [current_dw].[Process Step] on [Process Step ID] = [FK Process Step ID]
where [FK Feature ID] >= 5997
order by [Feature ID], [Assignment Start Date];

Expected Results

Time is consistently reported through the process steps entirely as either UTC or Server time

Actual Results

Time is reported in UTC in some steps and server time in others.

Example:

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available