Start timestamp saved incorrectly in DB, when Idea to Project conversion happens

Products

• Clarity PPM On Premise
• Clarity PPM SaaS

Issue/Introduction

Steps to Reproduce:
1. Make Studio changes:
    a. Change display type of 'Start' attribute:
        Classic UI -> Administration -> Objects -> Project object -> Views -> Fields [against 'Project Properties' row] -> Search for 'Start' attribute -> Properties -> Display Type = 'Date and Time'
    b. Set a default against 'Start' attribute:
        Classic UI -> Administration -> Objects -> Project object -> Attributes -> 'Start' attribute -> set 'Default Date' = '4/30/2024 8AM: 00'
2. Create a Project template:
    a. Classic UI -> Home -> Projects -> New -> Provide 'Name' and 'ID'. Set 'Start Date' time stamp to 8 AM
    b. Properties -> Settings -> 'Template' = YES
3. Check timestamp saved in DB using the following query. The template created would be amongst the first few records:
    SELECT
        id,
        name,
        code,
        schedule_start,
        schedule_finish
    FROM
        inv_investments
    ORDER BY
        created_date DESC;
4. Create a Project from template directly in the Modern UX
    Modern UX -> Projects Grid -> New from Template -> Choose the template from step 2
5. Check timestamp against the newly created Project using the query from step 3

Expected Results: The timestamp in the 'schedule_start' column is set to 8 AM
Actual Results: The timestamp in the 'schedule_start' column is set to 8 AM

6. Convert an Idea to a Project. Use the same template to do this
    Modern UX -> Ideas Grid -> Choose an Idea that is approved -> Convert to Project -> Choose template from step 2
7. Check timestamp against the newly created Project using the query from step 3

Expected Results: The timestamp in the 'schedule_start' column is set to 8 AM
Actual Results: The timestamp in the 'schedule_start' column is set to 12 AM

Cause

DE80716

Resolution

DE80716 is fixed in 16.2.3.